bug-bash  

Messages by Thread

• [bug #68307] The time command produces invalid output in edge case nilpotence
• GLOBIGNORE Stan Marsh
  • Re: GLOBIGNORE Greg Wooledge
  • Re: GLOBIGNORE Stan Marsh
  • Re: GLOBIGNORE Chet Ramey
  • Re: GLOBIGNORE Koichi Murase
  • Re: GLOBIGNORE Chet Ramey
  • Re: GLOBIGNORE Zachary Santer
  • Re: GLOBIGNORE Stan Marsh
  • Re: GLOBIGNORE Stan Marsh
  • Re: GLOBIGNORE Stan Marsh
• [PATCH] Add @R parameter transform to reverse expansion order Jackson Hansen
  • Re: [PATCH] Add @R parameter transform to reverse expansion order Chet Ramey
• add EXAMPLES section to bash man page SSS foundation
  • Re: add EXAMPLES section to bash man page Chet Ramey
• Typo in the bash manual jjj g
• Possible busy-loop in signal handling with a trap calling an external command František Šumšal
  • Re: Possible busy-loop in signal handling with a trap calling an external command Zachary Santer
  • Re: Possible busy-loop in signal handling with a trap calling an external command Chet Ramey
• Array functions Laurent Lyaudet
  • Re: Array functions Greg Wooledge
• $!() gives a list of files Andrew Young
  • Re: $!() gives a list of files Matti Andreas Kähäri
  • Re: $!() gives a list of files Stan Marsh
• New loadable builtin: rev Duncan Roe
  • Re: New loadable builtin: rev Duncan Roe
  • Re: New loadable builtin: rev Oğuz
  • Re: New loadable builtin: rev Duncan Roe
  • Re: New loadable builtin: rev Oğuz
  • [PATCH] rev: fix some issues Grisha Levit
• [bug #68233] Runing & using `bind -x '"\ez":"fg"'` cause tab completion to print white space anonymous
• LINES and COLUMNS Zachary Santer
  • Re: LINES and COLUMNS Martin D Kealey
  • Re: LINES and COLUMNS Koichi Murase
  • Re: LINES and COLUMNS Zachary Santer
  • Re: LINES and COLUMNS Chet Ramey
• feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Zachary Santer
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Koichi Murase
  • feature request: ${[@]| command; } and ${[*]| command; } funsubs to expand to all elements of the local array REPLY Zachary Santer
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Chet Ramey
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Koichi Murase
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Chet Ramey
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Koichi Murase
  • Re: feature request: ${@ command; } and ${* command; } funsubs to expand to all elements of the local array REPLY Chet Ramey
  • Re: feature request: ${[@]| command; } and ${[*]| command; } funsubs to expand to all elements of the local array REPLY Zachary Santer
  • Re: feature request: ${[@]| command; } and ${[*]| command; } funsubs to expand to all elements of the local array REPLY Koichi Murase
• BUG: Brace expansions do not support any type of variable. Invert Ignas
  • Re: BUG: Brace expansions do not support any type of variable. Zachary Santer
  • Re: non-bug: Brace expansions do not support any type of variable. Martin D Kealey
  • Re: BUG: Brace expansions do not support any type of variable. Chet Ramey
• REVERSE_LIST macro aliasing issue Sam James
  • Re: REVERSE_LIST macro aliasing issue Andreas Schwab
• [PATCH] Fix complete -p with commands starting with - Étienne Barrié
  • Re: [PATCH] Fix complete -p with commands starting with - Chet Ramey
• [bug #68188] "info" command not found in the italian version of GNU bash 5.2.37(1)-release anonymous
  • Re: [bug #68188] "info" command not found in the italian version of GNU bash 5.2.37(1)-release Félix Hauri via Bug reports for the GNU Bourne Again SHell
• [gnu.org #2263310] typo on bash manual Arrays Therese Godefroy via RT
• Pipe makes subshell crash with stack overflow Manuel Wagesreither
  • Re: Pipe makes subshell crash with stack overflow Chet Ramey
• [bug #68164] Access violation crashes p.loschenok
• [bug #68163] Heap-buffer-overflow(read) crashes p.loschenok
• [bug #68162] TrapSignal crashes p.loschenok
• [bug #68159] Out of memmory crashes p.loschenok
• loadable cut builtin gives assertion botched in free() Duncan Roe
  • Re: loadable cut builtin gives assertion botched in free() Chet Ramey
• Raw ^M in xtrace output Marcel Schnippe
  • Re: Raw ^M in xtrace output Chet Ramey
• Parameter transformation `@A` on array member A4-Tacks
  • Re: Parameter transformation `@A` on array member Chet Ramey
• Correction in GNU Bash Manual HTML version Anshuman Khanna
  • Re: Correction in GNU Bash Manual HTML version Chet Ramey
• [bug #68131] Shell script misbehaves when edited Matt
  • Re: [bug #68131] Shell script misbehaves when edited Stan Marsh
  • Re: [bug #68131] Shell script misbehaves when edited Greg Wooledge
  • Re: [bug #68131] Shell script misbehaves when edited Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: [bug #68131] Shell script misbehaves when edited Greg Wooledge
  • Re: [bug #68131] Shell script misbehaves when edited Chet Ramey
  • Re: [bug #68131] Shell script misbehaves when edited Robert Elz
  • Re: [bug #68131] Shell script misbehaves when edited Stan Marsh
  • Re: [bug #68131] Shell script misbehaves when edited Robert Elz
  • Re: [bug #68131] Shell script misbehaves when edited Zachary Santer
  • Re: [bug #68131] Shell script misbehaves when edited Félix Hauri via Bug reports for the GNU Bourne Again SHell
• inconsistent behavior of extglobs at start of pattern re dotfiles Isaac Z. Schlueter
  • Re: inconsistent behavior of extglobs at start of pattern re dotfiles Chet Ramey
• [bug] Bash crash when malloc is called in a signal handler. fengfei . xi
  • Re: [bug] Bash crash when malloc is called in a signal handler. Chet Ramey
• [bug #68128] History not saved if we get SIGHUP during PROMPT_COMMAND Ville Viinikka
• [PATCH] skip_to_histexp: fix out-of-range access Grisha Levit
  • Re: [PATCH] skip_to_histexp: fix out-of-range access Chet Ramey
• [bug #68122] history is not saved on terminal close Andrey
• Re: Best way to expand a boolean into a string when true Martin D Kealey
  • Re: Best way to expand a boolean into a string when true Laurent Lyaudet
  • Re: Best way to expand a boolean into a string when true Wiley Young
• The exit code for the foreground command unexpectedly became 0. 王伟
  • Re: The exit code for the foreground command unexpectedly became 0. 王伟
  • Re: The exit code for the foreground command unexpectedly became 0. Chet Ramey
  • Re: The exit code for the foreground command unexpectedly became 0. 王伟
  • Re: The exit code for the foreground command unexpectedly became 0. 王伟
  • Re: The exit code for the foreground command unexpectedly became 0. Chet Ramey
• autom4te.cache in release tarball for Bash 5.3 Gioele Barabucci
• bash continues after kill(self, TERM) on reboot Daniel Villeneuve
  • Re: bash continues after kill(self, TERM) on reboot Chet Ramey
  • Re: bash continues after kill(self, TERM) on reboot Daniel Villeneuve
  • Re: bash continues after kill(self, TERM) on reboot Chet Ramey
  • Re: bash continues after kill(self, TERM) on reboot Daniel Villeneuve
  • Re: bash continues after kill(self, TERM) on reboot Chet Ramey
  • Re: bash continues after kill(self, TERM) on reboot Daniel Villeneuve
• Kill sends signal to wrong process group with job control enabled Ben Ashton
  • Re: Kill sends signal to wrong process group with job control enabled Martin D Kealey
  • Re: Kill sends signal to wrong process group with job control enabled Ben Ashton
  • Re: Kill sends signal to wrong process group with job control enabled Robert Elz
  • Re: Kill sends signal to wrong process group with job control enabled Ben Ashton
  • Re: Kill sends signal to wrong process group with job control enabled Oğuz
  • Re: Kill sends signal to wrong process group with job control enabled Ben Ashton
  • Re: Kill sends signal to wrong process group with job control enabled Robert Elz
  • Re: Kill sends signal to wrong process group with job control enabled Chet Ramey
  • Re: Kill sends signal to wrong process group with job control enabled Robert Elz
  • Re: Kill sends signal to wrong process group with job control enabled Chet Ramey
  • Re: Kill sends signal to wrong process group with job control enabled Chet Ramey
• [bug #68094] in bash a forward slash is added at end of commands in tab completion if there is a directory with the same name tmp0x
• forward slash is added at end of commands in tab completion if there is a directory with the same name &&&&&&&&&&
  • Re: forward slash is added at end of commands in tab completion if there is a directory with the same name Chet Ramey
  • Re: forward slash is added at end of commands in tab completion if there is a directory with the same name Martin D Kealey
  • Re: forward slash is added at end of commands in tab completion if there is a directory with the same name &&&&&&&&&&
  • Re: forward slash is added at end of commands in tab completion if there is a directory with the same name Chet Ramey
• [PATCH] fix: should be indentation Weixie Cui
  • Re: [PATCH] fix: should be indentation Chet Ramey
• fltexpr LAND && LOR || broken newsbash--- via Bug reports for the GNU Bourne Again SHell
  • Re: fltexpr LAND && LOR || broken Andreas Schwab
  • Re: fltexpr LAND && LOR || broken Greg Wooledge
  • Re: fltexpr LAND && LOR || broken Chet Ramey
• making a variable local counts as a statement as per $? Luca Saiu
  • Re: making a variable local counts as a statement as per $? Oğuz
  • Re: making a variable local counts as a statement as per $? Luca Saiu
  • Re: making a variable local counts as a statement as per $? David
  • Re: making a variable local counts as a statement as per $? Luca Saiu
• [PATCH] `compopt -o nosort` with duplicates intact aqzkwaaq
  • Re: [PATCH] `compopt -o nosort` with duplicates intact Chet Ramey
  • Re: [PATCH] `compopt -o nosort` with duplicates intact Martin D Kealey
• bash --More-- prompt should show more Dan Jacobson
  • Re: bash --More-- prompt should show more Martin D Kealey
  • Re: bash --More-- prompt should show more Dan Jacobson
  • Re: bash --More-- prompt should show more Chet Ramey
  • Re: bash --More-- prompt should show more Dan Jacobson
  • Re: bash --More-- prompt should show more Chet Ramey
• coprocs some more Zachary Santer
  • Re: coprocs some more Chet Ramey
• Bash Feature Proposal Eric Lovejoy via Bug reports for the GNU Bourne Again SHell
  • Re: Bash Feature Proposal Greg Wooledge
  • Re: Bash Feature Proposal Robert Elz
  • Re: Bash Feature Proposal Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Bash Feature Proposal Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Bash Feature Proposal Robert Elz
  • Re: Bash Feature Proposal Petr Derian
  • Re: Bash Feature Proposal Eric Lovejoy via Bug reports for the GNU Bourne Again SHell
  • Re: Bash Feature Proposal Stan Marsh
• Suggested addition for "help source" Duncan Roe
  • Re: Suggested addition for "help source" Chet Ramey
  • Re: Suggested addition for "help source" Duncan Roe
• bash 'read' doesn't have exit status >1 on error Paul Eggert
  • Re: bash 'read' doesn't have exit status >1 on error Chet Ramey
• read -d no longer accepts NUL as line delimiter from tty Martin D Kealey
  • Re: read -d no longer accepts NUL as line delimiter from tty Chet Ramey
• bash failed to start with valgrind Masanari Iida
  • Re: bash failed to start with valgrind Chet Ramey
• Trivia (Was: Should we use [[ or should we use [ when the later will do?) Stan Marsh
• Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) Stan Marsh
  • Re: Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) G. Branden Robinson
  • Re: Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) Robert Elz
• Missing close parenthesis on page 117 of reference manual Anselm Schüler
  • Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
  • Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
  • Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
  • Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
  • Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
  • Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
• [bug #68003] Single completion doesn't get selected anonymous
• Execution of subsequent commands after a command crashes. 王伟
  • Re: Execution of subsequent commands after a command crashes. Andreas Kähäri
  • Re: Execution of subsequent commands after a command crashes. 王伟
  • Re: Execution of subsequent commands after a command crashes. Chet Ramey
  • Re: Execution of subsequent commands after a command crashes. Robert Elz
  • Re: Execution of subsequent commands after a command crashes. Chet Ramey
  • Re: Execution of subsequent commands after a command crashes. Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Execution of subsequent commands after a command crashes. Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Fwd: Re: Execution of subsequent commands after a command crashes. Chet Ramey
• Commentary on: Bash Command Leads to ... Stan Marsh
  • Re: Commentary on: Bash Command Leads to ... Chet Ramey
  • Re: Commentary on: Bash Command Leads to ... Stan Marsh
  • Re: Commentary on: Bash Command Leads to ... Greg Wooledge
  • Re: Commentary on: Bash Command Leads to ... Andrew Church
  • Re: Commentary on: Bash Command Leads to ... Chet Ramey
  • Re: Commentary on: Bash Command Leads to ... Stan Marsh
• Re: Bash Command Leads to CLI No Longer Drawing Commands Martin D Kealey
• Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Jari Aalto
  • Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Robert Elz
  • Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Chet Ramey
• [bug #67957] Syntax error messages permanently change after interrupting process/command substitution parsing anonymous
• "echo $((0x))" is accepted, treated as 0x0 Denys Vlasenko
  • Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Kähäri

• Earlier messages