[PATCH 1/1] Exit status of fc -e is the wrong way around

Hello Bash developers! 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' -DLOC

NULL pointer dereference crash

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/local/share

Re: bash 4.4 messed up input with certain background processes

On 6/29/16 11:22 PM, Grisha Levit wrote: > Thanks, the -n option does work around this. > I was very surprised to see input going to a backgrounded process You shouldn't be. When job control is active, bash doesn't modify the standard input of any background process it starts, in case the job ge

Re: NULL pointer dereference crash

On 6/30/16 5:43 AM, Nicolas Vivet wrote: > Bash Version: 4.3 > Patch Level: 0 > Release Status: release > > Description: > bash dereferences a NULL pointer when the last call to fork has failed. Thanks for the report. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

Re: [PATCH 1/1] Exit status of fc -e is the wrong way around

On 6/30/16 7:02 AM, Ingo Karkat wrote: > Bash Version: 4.3 > Patch Level: 46 > Release Status: release > Also seen in prior versions, at least down to 4.2.46(1)-release > > Description: > > I'm trying to edit and recall a previous command with Bash's built-in "fc -e > vi" command, but somehow t