Re: large exit values (>255)

Mike Frysinger wrote: > $ true > $ echo ' > > $ echo $? > 258 > > $ true > $ echo ' > > $ echo ' > > $ echo $? > 386 Just tested it, hopefully it's as easy as changing every itos (last_command_exit_value) to itos (last_command_exit_value & 0xFF) in subst.c (seems 2 times). I don't provid

Re: large exit values (>255)

Mike Frysinger wrote: > $ true > $ echo ' > > $ echo $? > 258 > > $ true > $ echo ' > > $ echo ' > > $ echo $? > 386 > > that doesnt seem right to me :) > > the first test seems fine, and older versions of bash would set 258 for the > second test (not sure if it's correct though), but the t

Re: graphic characters set

On Feb 25, 4:20 am, Antonio Macchi wrote: > this command should starts the graphic character set (to create masks) > > $ tput smacs > > but, using aterm or Eterm, it does not work > > but it works using this form (lieing...) > > $ TERM=xterm tput smacs > > does anyone know where is the problem? t

Re: bash-4.0: parser complains on `|& {}' statement

Evgeniy Zhemchugov wrote: > Configuration Information > 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/locale' >

Re: Problem with function cd in bash 4.0

On Wednesday 25 February 2009 16:21:47 Chet Ramey wrote: > > > Yep, it's a bug. Try the attached patch; it works for me. > > > > this introduces a bug of it's own though :/. you can no longer use > > ctrl+c to escape from unbalanced quotes. > > > > - type: echo ' > > - hit enter > > - hit ctrl+c

Re: Problem with function cd in bash 4.0

> > Yep, it's a bug. Try the attached patch; it works for me. > > this introduces a bug of it's own though :/. you can no longer use ctrl+c to > escape from unbalanced quotes. > > - type: echo ' > - hit enter > - hit ctrl+c over and over > - bash still waits for the ' to be balanced Still not

Re: Problem with function cd in bash 4.0

Mike Frysinger wrote: > this introduces a bug of it's own though :/. you can no longer use ctrl+c to > escape from unbalanced quotes. > > - type: echo ' > - hit enter > - hit ctrl+c over and over > - bash still waits for the ' to be balanced Interesting. This happens only on Linux. FreeBSD,

Re: Problem with function cd in bash 4.0

On Monday 23 February 2009 23:02:56 Chet Ramey wrote: > Bernd Eggink wrote: > > I normally wrap the builtin cd into a function cd, which does some > > additional things and then calls the builtin. Example: > > > >function cd > >{ > > local list=$(echo *.bui) > > # ... > > bu

large exit values (>255)

seems there's a way to get bash to report exit values greater than 255 ... since it requires certain key presses, things in between <...> means a key press rather than typing literally ... $ true $ echo ' $ echo $? 128 $ echo ' $ echo ' $ echo $? 128 $ true $ echo ' $ echo $? 258 $ true $

Re: free: called with unallocated block argument

On Wednesday 25 February 2009 09:06:21 Roman Rakus wrote: > It will be useful to have bash-4.0-patches available as it was for past > versions. When are you planning to do that? Thanks. ive been adding them to Gentoo as Chet posts them ... http://sources.gentoo.org/app-shells/bash/files/bash-4.0-

Re: crash encountered. repeatable.

> Machine Type: i686-pc-linux-gnu > > Bash Version: 4.0 > Patch Level: 0 > Release Status: release > > Description: > Crash occurs when using bash-completion 20060301 > to complete a cd command to a directory. > bash 4.0; readline 6.0 and bash-completion 20060301 are installed. > The prob

Re: free: called with unallocated block argument

> It will be useful to have bash-4.0-patches available as it was for past > versions. When are you planning to do that? Thanks. I will release official bash-4.0 patches as I have a chance. The posts to the mailing list are to get fixes in peoples' hands quickly. Chet -- ``The lyf so short, t

Re: bash stuck in a loop defining arrays

> Thanks, unfortunately it seems that this patch isn't enough as it > also happens with a simpler test case: > > bash-4.0$ declare -A array > bash-4.0$ declare array[foo]=bar That's actually a different problem, a fix for which I was thinking about before receiving your message. :-) Chet -- `

crash encountered. repeatable.

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-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

examples/loadable/finfo.c missing cast

imadev:~$ enable -f /var/tmp/bash-4.0/examples/loadables/finfo finfo imadev:~$ ls -l .bashrc -rw-r--r-- 1 wooledgpgmr 331 Sep 16 14:30 .bashrc imadev:~$ finfo -s .bashrc 316732948 imadev:~$ finfo -s .bashrc 317115222 --- finfo.c.origWed Feb 25 10:07:12 2009 +++ finfo.c

Re: bash stuck in a loop defining arrays

On Wed, Feb 25, 2009 at 4:46 PM, Chet Ramey wrote: >> Machine Type: i386-unknown-openbsd4.4 >> >> Bash Version: 4.0 >> Patch Level: 0 >> >> Description: >>         playing with the associative arrays, bash ends up in what appears >> to be a busy loop that I cannot interupt with C-c >> >> Repeat-By

Re: bash stuck in a loop defining arrays

> Machine Type: i386-unknown-openbsd4.4 > > Bash Version: 4.0 > Patch Level: 0 > > Description: > playing with the associative arrays, bash ends up in what appears > to be a busy loop that I cannot interupt with C-c > > Repeat-By: > > > bash-4.0$ declare -A array > bash-4.0$ declare ar

Re: free: called with unallocated block argument

Chet Ramey wrote: p...@arcturus.universe wrote: Bash Version: 4.0 Patch Level: 0 Release Status: release Description: Problem with auto completion : ls[space][TAB] gives the follwing abort : malloc: /Users/chet/src/bash/src/parse.y:5561: assertion botched free: calle

Re: coproc command doesn't accept NAME arg

Jan Schampera wrote: > Tim Hatch wrote: > >> Pilot:~/tmp/bash-4.0 tim$ coproc NAME ls >> [1] 18474 >> Pilot:~/tmp/bash-4.0 tim$ ./bash: line 32: NAME: command not found >> >> [1]+ Exit 127coproc COPROC NAME ls > > For some reason it expects a compound command on n

[OT] graphic characters set

this command should starts the graphic character set (to create masks) $ tput smacs but, using aterm or Eterm, it does not work but it works using this form (lieing...) $ TERM=xterm tput smacs does anyone know where is the problem?