BUG: bash-4.0.17 and SIGWINCH during initialization

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

Re: backward-kill-word is not refreshing correctly

> Machine Type: i686-pc-linux-gnu > > Bash Version: 4.0 > Patch Level: 10 > Release Status: release > > Description: > When I type a long string of text and start pressing ctrl-W to > backwards-kill words, bash deletes the words but doesn't visually refresh > (the words still appear on th

bash associative arrays... my personal trick... waht do you think?

function idx { eval 'case $1 in '${cases[*]}' *) [ "$1" ] && { cases=( ${cases[*]} '\''"'\''$1'\''") echo '${#cases[*]}';;'\'' ); echo '${#cases[*]}';}; esac'; } idx all 0 idx all 0 idx jhon 1 idx all 0 as you can see the function return different values for different strings so associative array

Re: DEBUG trap breaks pipelines

l...@upc.ua wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' > -DCONF_VENDOR='redhat

Re: backward-kill-word is not refreshing correctly

And help I will definitely attempt. Here are the requested values: col_lendiff = 5 _rl_last_c_pos = 194 _rl_screenwidth = 126 Some random other variables, in case they end up being requested: lendiff = 5 old = 8403456 new = 8457216 ne = 8457410 oe = 8403655 temp = 0 My cursor is definitely not

Re: backward-kill-word is not refreshing correctly

Jay Freeman (saurik) wrote: >>> When I type a long string of text and start pressing ctrl-W to >>> backwards-kill words, bash deletes the words but doesn't visually refresh >>> (the words still appear on the command line). This was not occurring for me >>> in the 3.x series of Bash. > >> I havi

Re: how to pass arguments with space inside?

On Fri, 10 Apr 2009, Greg Wooledge wrote: On Fri, Apr 10, 2009 at 12:02:56AM -0700, lehe wrote: The reason why I don't use "$@" is that the arguments to the bash script is not completely those for the executable. Some of them are just arguments only to the bash script. So actually the script is