bug-bash  

Messages by Thread

• `help cut` doesn't document what -a does Duncan Roe
• Tilde expansion in PATH in POSIX-Mode Martin Schulte
  • Re: Tilde expansion in PATH in POSIX-Mode Léa Gris
  • Re: Tilde expansion in PATH in POSIX-Mode Lawrence Velázquez
  • Re: Tilde expansion in PATH in POSIX-Mode Martin Schulte
• Message "You have new mail ..." interrupts programmable completion Troy Loveday
  • Re: Message "You have new mail ..." interrupts programmable completion Chet Ramey
  • Re: Message "You have new mail ..." interrupts programmable completion Troy Loveday
• combination of source and && does not result in current alias to be expanded Bob Mroczka
  • Re: combination of source and && does not result in current alias to be expanded Greg Wooledge
  • Re: combination of source and && does not result in current alias to be expanded Lawrence Velázquez
• grouping via {} fails after "test $PIPESTATUS" Steve Newcomb
  • Re: grouping via {} fails after "test $PIPESTATUS" Greg Wooledge
  • Re: grouping via {} fails after "test $PIPESTATUS" microsuxx
  • Re: grouping via {} fails after "test $PIPESTATUS" Chet Ramey
  • grouping via {} fails after "test $PIPESTATUS" Stan Marsh
• Weird -s test behavior Stephen Leaf
  • Re: Weird -s test behavior Grisha Levit
• [PATCH] bash-5.3-rc1 FTBFS when cross compiling with gcc-15 Bruce Dubbs
  • Re: [PATCH] bash-5.3-rc1 FTBFS when cross compiling with gcc-15 Oğuz
  • Re: [PATCH] bash-5.3-rc1 FTBFS when cross compiling with gcc-15 Chet Ramey
  • Re: [PATCH] bash-5.3-rc1 FTBFS when cross compiling with gcc-15 Chet Ramey
• Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E FunnyMan Computer
  • Re: Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E Chet Ramey
  • Re: Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E FunnyMan Computer
  • Re: Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E Greg Wooledge
  • Re: Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E Andreas Schwab
  • Re: Difference in POSIX regular expression for bash's '=~' operator and POSIXLY_CORRECT grep -E Wiley Young
• What is the status of bash-5.3? Bruce Dubbs
  • Re: What is the status of bash-5.3? Todd Zullinger
  • Re: What is the status of bash-5.3? Chet Ramey
• ${subscriptref} triggers nounset, but $subscriptref does not Emanuele Torre
  • Re: ${subscriptref} triggers nounset, but $subscriptref does not Emanuele Torre
  • Re: ${subscriptref} triggers nounset, but $subscriptref does not Chet Ramey
• Cross-Compile - Makefile - Install-strip NR
  • Re: Cross-Compile - Makefile - Install-strip Chet Ramey
• Bash does not complete the filename once the situation becomes singular Adam Purkrt
  • Re: Bash does not complete the filename once the situation becomes singular Chet Ramey
• Brace expansion change on devel Sam James
  • Re: Brace expansion change on devel Chet Ramey
  • Re: Brace expansion change on devel Sam James
• [PATCH] Fix link error on GNU/Hurd. Collin Funk
  • Re: [PATCH] Fix link error on GNU/Hurd. Chet Ramey
  • Re: [PATCH] Fix link error on GNU/Hurd. Collin Funk
• feature request: for name ... in word ...; do list; done Zachary Santer
• SourceAv in xparse_dolparen when trying to compare with rvalue Александр Ушаков
  • Re: SourceAv in xparse_dolparen when trying to compare with rvalue Grisha Levit
  • Re: SourceAv in xparse_dolparen when trying to compare with rvalue Chet Ramey
  • Re: SourceAv in xparse_dolparen when trying to compare with rvalue Александр Ушаков
  • Re: SourceAv in xparse_dolparen when trying to compare with rvalue Martin D Kealey
  • Re: SourceAv in xparse_dolparen when trying to compare with rvalue Chet Ramey
• SourceAv in rewind_input_string when trying to compare with rvalue Александр Ушаков
  • Re: SourceAv in rewind_input_string when trying to compare with rvalue Grisha Levit
  • Re: SourceAv in rewind_input_string when trying to compare with rvalue Chet Ramey
• Bug in Bash Autocompletion: Hidden File, ...Hiding-From-You, Autocompleted Without Dot Prefix Tanmay Jagtap
  • Re: Bug in Bash Autocompletion: Hidden File, ...Hiding-From-You, Autocompleted Without Dot Prefix Chet Ramey
  • Re: Bug in Bash Autocompletion: Hidden File, ...Hiding-From-You, Autocompleted Without Dot Prefix Tanmay Jagtap
  • Re: Bug in Bash Autocompletion: Hidden File, ...Hiding-From-You, Autocompleted Without Dot Prefix Robert Elz
  • Re: Bug in Bash Autocompletion: Hidden File, ...Hiding-From-You, Autocompleted Without Dot Prefix Chet Ramey
• $* in here-document Martijn Dekker
  • Re: $* in here-document Chet Ramey
• Heap-buffer-overflow in read_token_word() when read element with -1 index Александр Ушаков
  • Re: Heap-buffer-overflow in read_token_word() when read element with -1 index Chet Ramey
  • Re: Heap-buffer-overflow in read_token_word() when read element with -1 index Grisha Levit
  • Re: Heap-buffer-overflow in read_token_word() when read element with -1 index Chet Ramey
  • Re: Heap-buffer-overflow in read_token_word() when read element with -1 index Martin D Kealey
• [bug #67045] bash parsing error, when using readline, backslashes, and <Ctrl-d> anonymous
• Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters Greg Wooledge
  • Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters Chet Ramey
  • Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters Stephane Chazelas
  • Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters Chet Ramey
  • Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters Félix Hauri
• Heap-buffer-overflow in parse_matched_pair when push_delimiter (dstack, ch) macros opens up Александр Ушаков
  • Re: Heap-buffer-overflow in parse_matched_pair when push_delimiter (dstack, ch) macros opens up Chet Ramey
• Bash documentation is missing ID anchor Antti Savolainen
  • Re: Bash documentation is missing ID anchor Chet Ramey
• 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 Ángel
  • 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

• Earlier messages