Using the arrow keys in vi-insert-mode frequently causes text to be deleted.

From: Wes To: bug-bash@gnu.org Subject: Using the arrow keys in vi-insert-mode frequently causes text to be deleted. Configuration Information [Automatically generated, do not change]: Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DC

Re: variable scope

Antonio Macchi wrote: > $ a=OUTSIDE > > $ f1 () { local a=INSIDE; f2; } > > $ f2 () { echo "before: $a"; > unset a; > echo "after: $a"; } > > > $ f3 () { local a=INSIDE; > echo "before: $a"; > unset a; > echo "after: $a"; } > > > $ f1 > before

Re: =~ behaves differently in bash 3.2 and 3.0

Clark J. Wang wrote: > In bash 3.0.14, the condition [[ file.txt =~ .*\\.txt\$ ]] returns TRUE but > in 3.2.39 it returns FALSE. But with the shopt option `compat31' set it also > returns TRUE. Is that reasonable? In the bash manual, `compat31' makes sense > only for quoted patterns. The string .*\

Re: with bash 3.2 from source: hashmarks inside backticks cause parse error

Tim München wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: gcc > Compilation > CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' > -DCONF_MACHTYPE='i686-redhat-linux-gnu' -DCONF_VENDOR='redhat' > -

with bash 3.2 from source: hashmarks inside backticks cause parse error

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPA

Re: =~ behaves differently in bash 3.2 and 3.0

2008-10-24, 14:56(+08), Clark J. Wang: > In bash 3.0.14, the condition [[ file.txt =~ .*\\.txt\$ ]] returns TRUE but > in 3.2.39 it returns FALSE. But with the shopt option `compat31' set it also > returns TRUE. Is that reasonable? In the bash manual, `compat31' makes sense > only for quoted patter

Re: =~ behaves differently in bash 3.2 and 3.0

Clark J. Wang schrieb: In bash 3.0.14, the condition [[ file.txt =~ .*\\.txt\$ ]] returns TRUE but in 3.2.39 it returns FALSE. But with the shopt option `compat31' set it also returns TRUE. Is that reasonable? In the bash manual, `compat31' makes sense only for quoted patterns. The string .*\\.tx

variable scope

$ a=OUTSIDE $ f1 () { local a=INSIDE; f2; } $ f2 () { echo "before: $a"; unset a; echo "after: $a"; } $ f3 () { local a=INSIDE; echo "before: $a"; unset a; echo "after: $a"; } $ f1 before: INSIDE after: OUTSIDE $ f3 before: INSIDE after: I