bug-bash  

Messages by Thread

• Surprising behavior with inline environment variable expansion Léa Gris
  • Re: Surprising behavior with inline environment variable expansion Andreas Schwab
  • Re: Surprising behavior with inline environment variable expansion Andreas Kähäri
  • Re: Surprising behavior with inline environment variable expansion Léa Gris
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Andreas Kähäri
  • Re: Surprising behavior with inline environment variable expansion Léa Gris
  • Re: Surprising behavior with inline environment variable expansion Greg Wooledge
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Robert Elz
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
  • Re: Surprising behavior with inline environment variable expansion Lawrence Velázquez
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Robert Elz
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Chet Ramey
  • Re: Surprising behavior with inline environment variable expansion Léa Gris
• ;exit in bash history causes bash to exit Ethan Gascoigne
  • Re: ;exit in bash history causes bash to exit Martin Schulte
  • Re: ;exit in bash history causes bash to exit microsuxx
  • Re: ;exit in bash history causes bash to exit microsuxx
  • Re: ;exit in bash history causes bash to exit microsuxx
  • Re: ;exit in bash history causes bash to exit Greg Wooledge
  • Re: ;exit in bash history causes bash to exit microsuxx
  • Re: ;exit in bash history causes bash to exit Duncan Roe
  • Re: ;exit in bash history causes bash to exit Dale R. Worley
• [sr #111211] `pipefail` leak/disablement anonymous
  • Re: [sr #111211] `pipefail` leak/disablement Emanuele Torre
  • Re: [sr #111211] `pipefail` leak/disablement Martin D Kealey
• Re: Is this a bug? Collin Funk
• foo=bar baz=${|...;} cmd segfauls after running ... Emanuele Torre
  • Re: foo=bar baz=${|...;} cmd segfauls after running ... Chet Ramey
• [bug #66923] Manual states that $(cat x) and $(< x) being equivalent not strictly true anonymous
• Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Ionut Nicula
  • Re: Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Chet Ramey
  • Re: Ctrl+C during ~/.bashrc evaluation leads to unexpected behavior Martin D Kealey
• Heredoc with a multiline delimiter Nikola Novak via Bug reports for the GNU Bourne Again SHell
  • Re: Heredoc with a multiline delimiter Greg Wooledge
  • Re: Heredoc with a multiline delimiter Nikola Novak via Bug reports for the GNU Bourne Again SHell
  • Re: Heredoc with a multiline delimiter Robert Elz
  • Re: Heredoc with a multiline delimiter MacBeth
  • Re: Heredoc with a multiline delimiter microsuxx
  • Re: Heredoc with a multiline delimiter Lawrence Velázquez
  • Re: Heredoc with a multiline delimiter Chet Ramey
  • Re: Heredoc with a multiline delimiter Robert Elz
  • Re: Heredoc with a multiline delimiter MacBeth
  • Re: Heredoc with a multiline delimiter Robert Elz
  • Re: Heredoc with a multiline delimiter MacBeth
  • Re: Heredoc with a multiline delimiter Chet Ramey
• $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Greg Wooledge
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Robert Elz
  • Re: $*, and $IFS, again Steffen Nurpmeso
  • Re: $*, and $IFS, again Greg Wooledge
  • Re: $*, and $IFS, again Steffen Nurpmeso
• Degenerate case in brace expansion. Kaz Kylheku
  • Re: Degenerate case in brace expansion. Lawrence Velázquez
  • Re: Degenerate case in brace expansion. Chet Ramey
• Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Chet Ramey
  • Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Greg Wooledge
  • Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Lawrence Velázquez
  • Re: Bug: please document extended and alternate for loop syntax Chet Ramey
  • Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Chet Ramey
  • Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Oğuz
  • Re: Bug: please document extended and alternate for loop syntax Martin D Kealey
  • Re: Bug: please document extended and alternate for loop syntax Zachary Santer
  • Re: Bug: please document extended and alternate for loop syntax Lawrence Velázquez
  • Re: Bug: please document extended and alternate for loop syntax John Wiersba via Bug reports for the GNU Bourne Again SHell
  • Re: Bug: please document extended and alternate for loop syntax Phi Debian
• Possible bug for nested curly brace expansion Trond Endrestøl via Bug reports for the GNU Bourne Again SHell
  • Re: Possible bug for nested curly brace expansion microsuxx
  • Re: Possible bug for nested curly brace expansion Lawrence Velázquez
  • Re: Possible bug for nested curly brace expansion Kaz Kylheku
  • Re: Possible bug for nested curly brace expansion Lawrence Velázquez
• request: highlighting/combo boxes on commands jon usenet
• System deleted after using bash Austen Shanley
• Cosmetic issue in job control display of suspsended "command" command. Kaz Kylheku
  • Re: Cosmetic issue in job control display of suspsended "command" command. Chet Ramey
• How to fix this rjuliuscezar--- via Bug reports for the GNU Bourne Again SHell
  • Re: How to fix this microsuxx
• Unexpected $BASH_COMMAND after error in subshell Max Bowsher
  • Re: Unexpected $BASH_COMMAND after error in subshell Chet Ramey
  • Re: Unexpected $BASH_COMMAND after error in subshell microsuxx
• bash --pretty-print and pattern Timotei Campian
  • Re: bash --pretty-print and pattern Greg Wooledge
  • Re: bash --pretty-print and pattern Koichi Murase
  • Re: bash --pretty-print and pattern Greg Wooledge
  • Re: bash --pretty-print and pattern Andreas Kähäri
  • Re: bash --pretty-print and pattern Chet Ramey
  • Re: bash --pretty-print and pattern Koichi Murase
  • Re: bash --pretty-print and pattern Chet Ramey
  • Re: bash --pretty-print and pattern Timotei Campian
• [PATCH] Fix serialisation of read-write redirections Emanuele Torre
  • Re: [PATCH] Fix serialisation of read-write redirections Chet Ramey
• history writes to process substitution but errors reading it MacBeth
  • Re: history writes to process substitution but errors reading it MacBeth
  • Re: history writes to process substitution but errors reading it microsuxx
  • Re: history writes to process substitution but errors reading it Greg Wooledge
  • Re: history writes to process substitution but errors reading it microsuxx
  • Re: history writes to process substitution but errors reading it Chet Ramey
  • Re: history writes to process substitution but errors reading it Dale R. Worley
  • Re: history writes to process substitution but errors reading it Andreas Schwab
  • Re: history writes to process substitution but errors reading it Dale R. Worley
  • Re: history writes to process substitution but errors reading it Lawrence Velázquez
  • Re: history writes to process substitution but errors reading it Chet Ramey
• grammar error in Bash Reference Manual LY
  • Re: grammar error in Bash Reference Manual Lawrence Velázquez
• [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Andrés Rodríguez Reina
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Lawrence Velázquez
  • 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
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Lawrence Velázquez
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists microsuxx
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists microsuxx
  • 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
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Dale R. Worley
  • Re: [Suggestion] Add warning/error when using the tilde expansion in a folder where the tile-named file/folder exists Chet Ramey
• bug related to "set -e", "&&" and exit codes Nagy László Zsolt
  • Re: bug related to "set -e", "&&" and exit codes Lawrence Velázquez
• Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function carlyle_moulton
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Greg Wooledge
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Chet Ramey
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Robert Elz
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Greg Wooledge
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Robert Elz
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Greg Wooledge
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Robert Elz
  • Re: Bug in bash read builtin, info from while read REPLY leaking into separate red -r -p "$1" command in function Robert Elz
• filedescriptor leakage, potential crash Martin D Kealey
  • Re: filedescriptor leakage, potential crash Oğuz
  • Re: filedescriptor leakage, potential crash Martin D Kealey
  • Re: filedescriptor leakage, potential crash Chet Ramey
• return [n] documentation. Phi
  • Re: return [n] documentation. Greg Wooledge
  • Re: return [n] documentation. Chet Ramey
  • Re: return [n] documentation. Greg Wooledge
  • Re: return [n] documentation. Phi Debian
  • Re: return [n] documentation. Phi Debian
  • Re: return [n] documentation. Chet Ramey
  • Re: return [n] documentation. Chet Ramey
• Documentation inconsistency (?) Alexis Reynouard
  • Re: Documentation inconsistency (?) Andreas Kähäri
  • Re: Documentation inconsistency (?) Chet Ramey
• Patch on shellmath.sh from bash-doc v.5.2.32, r.1.fc41 Wiley Young
  • Re: Patch on shellmath.sh from bash-doc v.5.2.32, r.1.fc41 Chet Ramey
  • Re: Patch on shellmath.sh from bash-doc v.5.2.32, r.1.fc41 Chet Ramey
• Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility microsuxx
  • Re: Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility microsuxx
  • Re: Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility Chet Ramey
  • Re: Documenting Bash’s Tilde Expansion in PATH: A Proposal for Clarity and Compatibility Martin D Kealey
• DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Robert Elz
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam microsuxx
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Steffen Nurpmeso
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Steffen Nurpmeso
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Ángel
  • Re: DKIM Signature Issue Causing Mailing List Posts to be Marked as Spam Lawrence Velázquez
• [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Chet Ramey
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Chet Ramey
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) microsuxx
  • Re: [SPAM] Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [SPAM] Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) microsuxx
  • Re: [SPAM] Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) microsuxx
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Greg Wooledge
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Lawrence Velázquez
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Lawrence Velázquez
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Lawrence Velázquez
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Greg Wooledge
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Lawrence Velázquez
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Lawrence Velázquez
  • Re: [PATCH] Preserve echoctl setting in sh‑mode (lib/sh/shtty.c) Zeffie via Bug reports for the GNU Bourne Again SHell

• Earlier messages