bug-bash  

Messages by Date

• 2025/03/31 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/31 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/29 Re: Surprising behavior with inline environment variable expansion Robert Elz
• 2025/03/29 Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
• 2025/03/29 Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
• 2025/03/29 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/28 Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
• 2025/03/27 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/27 Re: Surprising behavior with inline environment variable expansion Léa Gris
• 2025/03/26 Re: ;exit in bash history causes bash to exit Dale R. Worley
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Robert Elz
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Chet Ramey
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Léa Gris
• 2025/03/26 Re: ;exit in bash history causes bash to exit microsuxx
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Andreas Kähäri
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Greg Wooledge
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Léa Gris
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Andreas Kähäri
• 2025/03/26 Re: Surprising behavior with inline environment variable expansion Andreas Schwab
• 2025/03/26 Surprising behavior with inline environment variable expansion Léa Gris
• 2025/03/26 Re: ;exit in bash history causes bash to exit Duncan Roe
• 2025/03/25 Re: ;exit in bash history causes bash to exit microsuxx
• 2025/03/25 Re: ;exit in bash history causes bash to exit microsuxx
• 2025/03/25 Re: ;exit in bash history causes bash to exit Greg Wooledge
• 2025/03/25 Re: ;exit in bash history causes bash to exit microsuxx
• 2025/03/25 Re: ;exit in bash history causes bash to exit Martin Schulte
• 2025/03/25 ;exit in bash history causes bash to exit Ethan Gascoigne
• 2025/03/24 Re: foo=bar baz=${|...;} cmd segfauls after running ... Chet Ramey
• 2025/03/24 Re: [sr #111211] `pipefail` leak/disablement Martin D Kealey
• 2025/03/24 Re: [sr #111211] `pipefail` leak/disablement Emanuele Torre
• 2025/03/24 [sr #111211] `pipefail` leak/disablement anonymous
• 2025/03/23 Re: Is this a bug? Collin Funk
• 2025/03/23 foo=bar baz=${|...;} cmd segfauls after running ... Emanuele Torre
• 2025/03/18 [bug #66923] Manual states that $(cat x) and $(< x) being equivalent not strictly true anonymous
• 2025/03/17 Re: Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Martin D Kealey
• 2025/03/17 Re: Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Chet Ramey
• 2025/03/17 Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Ionut Nicula
• 2025/03/17 Re: Heredoc with a multiline delimiter Chet Ramey
• 2025/03/17 Re: Heredoc with a multiline delimiter Chet Ramey
• 2025/03/16 Re: Heredoc with a multiline delimiter Lawrence Velázquez
• 2025/03/16 Re: Heredoc with a multiline delimiter MacBeth
• 2025/03/15 Re: Heredoc with a multiline delimiter Robert Elz
• 2025/03/15 Re: Heredoc with a multiline delimiter MacBeth
• 2025/03/15 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/15 Re: $*, and $IFS, again Robert Elz
• 2025/03/15 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/15 Re: Heredoc with a multiline delimiter Robert Elz
• 2025/03/15 Re: $*, and $IFS, again Robert Elz
• 2025/03/15 Re: $*, and $IFS, again Robert Elz
• 2025/03/15 Re: Heredoc with a multiline delimiter microsuxx
• 2025/03/15 Re: Heredoc with a multiline delimiter MacBeth
• 2025/03/15 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/15 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/15 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/15 Re: $*, and $IFS, again Greg Wooledge
• 2025/03/15 Re: $*, and $IFS, again Robert Elz
• 2025/03/15 Re: Heredoc with a multiline delimiter Robert Elz
• 2025/03/15 Re: Heredoc with a multiline delimiter Nikola Novak via Bug reports for the GNU Bourne Again SHell
• 2025/03/15 Re: $*, and $IFS, again Robert Elz
• 2025/03/15 Re: Heredoc with a multiline delimiter Greg Wooledge
• 2025/03/15 Heredoc with a multiline delimiter Nikola Novak via Bug reports for the GNU Bourne Again SHell
• 2025/03/15 Re: Bug: please document extended and alternate for loop syntax Phi Debian
• 2025/03/15 Re: Bug: please document extended and alternate for loop syntax Chet Ramey
• 2025/03/15 Re: Bug: please document extended and alternate for loop syntax Zachary Santer
• 2025/03/14 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/14 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/13 Re: $*, and $IFS, again Greg Wooledge
• 2025/03/13 Re: $*, and $IFS, again Robert Elz
• 2025/03/13 $*, and $IFS, again Steffen Nurpmeso
• 2025/03/13 Re: $*, and $IFS, again Steffen Nurpmeso
• 2025/03/12 Re: Bug: please document extended and alternate for loop syntax Martin D Kealey
• 2025/03/11 Re: Bug: please document extended and alternate for loop syntax Oğuz
• 2025/03/11 Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/10 Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/10 Re: Bug: please document extended and alternate for loop syntax Lawrence Velázquez
• 2025/03/10 Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/10 Re: Bug: please document extended and alternate for loop syntax Chet Ramey
• 2025/03/10 Re: Degenerate case in brace expansion. Chet Ramey
• 2025/03/08 Re: Degenerate case in brace expansion. Lawrence Velázquez
• 2025/03/08 Degenerate case in brace expansion. Kaz Kylheku
• 2025/03/08 Re: Possible bug for nested curly brace expansion microsuxx
• 2025/03/07 Re: Bug: please document extended and alternate for loop syntax Lawrence Velázquez
• 2025/03/07 Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/07 Re: Bug: please document extended and alternate for loop syntax Greg Wooledge
• 2025/03/07 Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/07 Re: Bug: please document extended and alternate for loop syntax Chet Ramey
• 2025/03/07 Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
• 2025/03/06 Re: Possible bug for nested curly brace expansion Lawrence Velázquez
• 2025/03/06 Re: Possible bug for nested curly brace expansion Kaz Kylheku
• 2025/03/06 Re: Possible bug for nested curly brace expansion Lawrence Velázquez
• 2025/03/06 Possible bug for nested curly brace expansion Trond Endrestøl via Bug reports for the GNU Bourne Again SHell
• 2025/03/05 request: highlighting/combo boxes on commands jon usenet
• 2025/03/04 System deleted after using bash Austen Shanley
• 2025/03/04 Re: Cosmetic issue in job control display of suspsended "command" command. Chet Ramey
• 2025/03/03 Cosmetic issue in job control display of suspsended "command" command. Kaz Kylheku
• 2025/02/26 Re: Unexpected $BASH_COMMAND after error in subshell microsuxx
• 2025/02/26 Re: Unexpected $BASH_COMMAND after error in subshell Chet Ramey
• 2025/02/24 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/24 Re: How to fix this microsuxx
• 2025/02/24 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/24 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/24 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/24 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/24 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/24 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/24 How to fix this rjuliuscezar--- via Bug reports for the GNU Bourne Again SHell
• 2025/02/24 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/23 Re: [sr #111166] ngettext syntax Martin D Kealey
• 2025/02/23 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/23 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/23 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/23 Unexpected $BASH_COMMAND after error in subshell Max Bowsher
• 2025/02/22 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/22 Re: [sr #111166] ngettext syntax Robert Elz
• 2025/02/22 Re: [sr #111166] ngettext syntax Robert Elz
• 2025/02/22 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/22 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/22 Re: [sr #111166] ngettext syntax Andreas Schwab
• 2025/02/21 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/21 Re: [sr #111166] ngettext syntax Robert Elz
• 2025/02/21 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/21 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/21 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/21 Re: [sr #111166] ngettext syntax Robert Elz
• 2025/02/21 Re: bash --pretty-print and pattern Timotei Campian
• 2025/02/21 Re: bash --pretty-print and pattern Chet Ramey
• 2025/02/21 Re: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/20 Re: [sr #111166] ngettext syntax Phi Debian
• 2025/02/20 Fwd: [sr #111166] ngettext syntax Chet Ramey
• 2025/02/20 Re: bash --pretty-print and pattern Koichi Murase
• 2025/02/20 Re: bash --pretty-print and pattern Chet Ramey
• 2025/02/20 Re: bash --pretty-print and pattern Andreas Kähäri
• 2025/02/20 Re: bash --pretty-print and pattern Greg Wooledge
• 2025/02/20 Re: bash --pretty-print and pattern Koichi Murase
• 2025/02/20 Re: bash --pretty-print and pattern Greg Wooledge
• 2025/02/20 bash --pretty-print and pattern Timotei Campian
• 2025/02/19 Re: history writes to process substitution but errors reading it Lawrence Velázquez
• 2025/02/19 Re: history writes to process substitution but errors reading it Dale R. Worley
• 2025/02/17 Re: Suggestion of wording for portion of man page Wiley Young
• 2025/02/14 Re: [PATCH] Fix serialisation of read-write redirections Chet Ramey
• 2025/02/14 [PATCH] Fix serialisation of read-write redirections Emanuele Torre
• 2025/02/14 Re: history writes to process substitution but errors reading it Chet Ramey
• 2025/02/14 Re: history writes to process substitution but errors reading it Andreas Schwab
• 2025/02/14 Re: history writes to process substitution but errors reading it Dale R. Worley
• 2025/02/14 Re: history writes to process substitution but errors reading it Chet Ramey
• 2025/02/14 Re: history writes to process substitution but errors reading it microsuxx
• 2025/02/14 Re: history writes to process substitution but errors reading it Greg Wooledge
• 2025/02/14 Re: history writes to process substitution but errors reading it microsuxx
• 2025/02/14 Re: history writes to process substitution but errors reading it MacBeth
• 2025/02/14 history writes to process substitution but errors reading it MacBeth
• 2025/02/13 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Chet Ramey
• 2025/02/13 Re: "printf %d ''" should diagnose the empty string Chet Ramey
• 2025/02/13 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/13 Re: "printf %d ''" should diagnose the empty string Greg Wooledge
• 2025/02/13 Re: "printf %d ''" should diagnose the empty string Oğuz
• 2025/02/13 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/12 Re: grammar error in Bash Reference Manual Lawrence Velázquez
• 2025/02/12 Re: "printf %d ''" should diagnose the empty string Oğuz
• 2025/02/12 grammar error in Bash Reference Manual LY
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Dale R. Worley
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Andrés Rodríguez Reina via Bug reports for the GNU Bourne Again SHell
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists microsuxx
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists microsuxx
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Lawrence Velázquez
• 2025/02/12 RE: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Andrés Rodríguez Reina
• 2025/02/12 Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Lawrence Velázquez
• 2025/02/12 [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Andrés Rodríguez Reina
• 2025/02/11 Re: bug related to "set -e", "&&" and exit codes Lawrence Velázquez
• 2025/02/11 bug related to "set -e", "&&" and exit codes Nagy László Zsolt
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string microsuxx
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string microsuxx
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string microsuxx
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/11 Re: "printf %d ''" should diagnose the empty string microsuxx
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Greg Wooledge
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string microsuxx
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Zachary Santer
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Lawrence Velázquez
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Chet Ramey
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Lawrence Velázquez
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Andreas Schwab
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Greg Wooledge
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Zachary Santer
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Zachary Santer
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Chet Ramey
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Chet Ramey
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Zachary Santer
• 2025/02/10 Re: "printf %d ''" should diagnose the empty string Phi Debian

• Earlier messages