bug-bash  

Messages by Thread

• Bash documentation is missing ID anchor Antti Savolainen
• Bash shell uses wrong language Kaulkwappe
  • Re: Bash shell uses wrong language Greg Wooledge
  • Re: Bash shell uses wrong language microsuxx
  • Re: Bash shell uses wrong language Chet Ramey
  • Re: Bash shell uses wrong language microsuxx
  • Re: Bash shell uses wrong language Chet Ramey
  • Re: Bash shell uses wrong language Greg Wooledge
  • Re: Bash shell uses wrong language Kaulkwappe
  • Re: Bash shell uses wrong language Chet Ramey
• tiny tweak to examples/functions/autoload.v3 (email addresses) Mark Kennedy
  • Re: tiny tweak to examples/functions/autoload.v3 (email addresses) Chet Ramey
• [sr #111224] custom completion not used after escaped semicolon anonymous
• Make cd built-in as resilient as mkdir -p built-in Laurent Lyaudet
  • Re: Make cd built-in as resilient as mkdir -p built-in Laurent Lyaudet
  • Re: Make cd built-in as resilient as mkdir -p built-in Laurent Lyaudet
  • Re: Make cd built-in as resilient as mkdir -p built-in Chet Ramey
  • Re: Make cd built-in as resilient as mkdir -p built-in Laurent Lyaudet
  • Re: Make cd built-in as resilient as mkdir -p built-in Chet Ramey
• Support ksh93 x=${<space>cmd;} Cedric Blancher
  • Re: Support ksh93 x=${<space>cmd;} Sam James
  • Re: Support ksh93 x=${<space>cmd;} Chet Ramey
  • Re: Support ksh93 x=${<space>cmd;} Dan Shelton
  • Re: Support ksh93 x=${<space>cmd;} Chet Ramey
  • Re: Support ksh93 x=${<space>cmd;} Dan Shelton
  • Re: Support ksh93 x=${<space>cmd;} Chet Ramey
  • Re: Support ksh93 x=${<space>cmd;} Phi Debian
  • Re: Support ksh93 x=${<space>cmd;} Dan Shelton
• Problem in trap help message Rafael Fontenelle via Bug reports for the GNU Bourne Again SHell
  • Re: Problem in trap help message Chet Ramey
• Bash-5.3-rc1 available Chet Ramey
• /dev/tcp feature request... A. James Lewis
  • Re: /dev/tcp feature request... MacBeth
  • Re: /dev/tcp feature request... MacBeth
  • Re: /dev/tcp feature request... MacBeth
  • Re: /dev/tcp feature request... Andreas Schwab
  • Re: /dev/tcp feature request... microsuxx
  • Re: /dev/tcp feature request... A. James Lewis
  • Re: /dev/tcp feature request... MacBeth
  • Re: /dev/tcp feature request... Chet Ramey
  • Re: /dev/tcp feature request... A. James Lewis
  • Re: /dev/tcp feature request... microsuxx
  • Re: /dev/tcp feature request... Chet Ramey
  • Re: /dev/tcp feature request... microsuxx
  • Re: /dev/tcp feature request... Chet Ramey
  • Re: /dev/tcp feature request... Oğuz
  • Re: /dev/tcp feature request... Greg Wooledge
  • Re: /dev/tcp feature request... Zachary Santer
  • Re: /dev/tcp feature request... MacBeth
• 3 updates for 5.3rc1 Duncan Roe
  • [PATCH 1/1] Build loadable builtin fltexpr; fix help for history and export Duncan Roe
  • Re: [PATCH 1/1] Build loadable builtin fltexpr; fix help for history and export Duncan Roe
  • Re: 3 updates for 5.3rc1 Chet Ramey
• 2.0..devel: `set -u; a=1; echo ${#a[@]}' fails Koichi Murase
  • Re: 2.0..devel: `set -u; a=1; echo ${#a[@]}' fails Chet Ramey
  • Re: 2.0..devel: `set -u; a=1; echo ${#a[@]}' fails Koichi Murase
  • Re: 2.0..devel: `set -u; a=1; echo ${#a[@]}' fails Chet Ramey
• Is this a bug? George R Goffe
  • Re: Is this a bug? Collin Funk
• Bash skips empty lines when reading history file in multiline mode Jens Schmidt
  • Re: Bash skips empty lines when reading history file in multiline mode Chet Ramey
  • Re: Bash skips empty lines when reading history file in multiline mode Jens Schmidt
  • Re: Bash skips empty lines when reading history file in multiline mode microsuxx
  • Re: Bash skips empty lines when reading history file in multiline mode microsuxx
• 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 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 Andreas Schwab
  • 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 Andreas Schwab
  • Re: Surprising behavior with inline environment variable expansion Andreas Kähäri
  • 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 Ethan Gascoigne
  • Re: ;exit in bash history causes bash to exit microsuxx
  • Re: ;exit in bash history causes bash to exit Dale R. Worley
  • 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
• [sr #111211] `pipefail` leak/disablement anonymous
  • Re: [sr #111211] `pipefail` leak/disablement Emanuele Torre
  • Re: [sr #111211] `pipefail` leak/disablement Martin D Kealey
• 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

• Earlier messages