bug-bash  

Messages by Date

• 2026/02/17 Re: Bash Feature Proposal Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2026/02/17 Re: Bash Feature Proposal Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2026/02/16 Re: coprocs some more Chet Ramey
• 2026/02/15 coprocs some more Zachary Santer
• 2026/02/11 Re: bash failed to start with valgrind Chet Ramey
• 2026/02/09 Re: Suggested addition for "help source" Duncan Roe
• 2026/02/09 Re: Suggested addition for "help source" Chet Ramey
• 2026/02/09 Re: Bash Feature Proposal Robert Elz
• 2026/02/09 Re: Bash Feature Proposal Robert Elz
• 2026/02/09 Re: Bash Feature Proposal Stan Marsh
• 2026/02/09 Re: Bash Feature Proposal Greg Wooledge
• 2026/02/09 Bash Feature Proposal Eric Lovejoy via Bug reports for the GNU Bourne Again SHell
• 2026/02/09 Re: bash 'read' doesn't have exit status >1 on error Chet Ramey
• 2026/02/08 Suggested addition for "help source" Duncan Roe
• 2026/02/08 bash 'read' doesn't have exit status >1 on error Paul Eggert
• 2026/02/05 Re: read -d no longer accepts NUL as line delimiter from tty Chet Ramey
• 2026/02/05 read -d no longer accepts NUL as line delimiter from tty Martin D Kealey
• 2026/02/04 bash failed to start with valgrind Masanari Iida
• 2026/02/04 Trivia (Was: Should we use [[ or should we use [ when the later will do?) Stan Marsh
• 2026/02/04 Fwd: Re: Execution of subsequent commands after a command crashes. Chet Ramey
• 2026/02/03 Re: Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) Robert Elz
• 2026/02/03 Re: Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) G. Branden Robinson
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
• 2026/02/03 Should we use [[ or should we use [ when the later will do? (Was: Execution of subsequent commands ...) Stan Marsh
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
• 2026/02/03 Re: Execution of subsequent commands after a command crashes. Chet Ramey
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Anselm Schüler
• 2026/02/03 Re: Missing close parenthesis on page 117 of reference manual Chet Ramey
• 2026/02/03 Missing close parenthesis on page 117 of reference manual Anselm Schüler
• 2026/02/03 Re: Commentary on: Bash Command Leads to ... Chet Ramey
• 2026/02/03 Re: Execution of subsequent commands after a command crashes. Chet Ramey
• 2026/02/03 Re: Commentary on: Bash Command Leads to ... Stan Marsh
• 2026/02/03 Re: Execution of subsequent commands after a command crashes. Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2026/02/03 Re: Execution of subsequent commands after a command crashes. Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2026/02/02 Re: Commentary on: Bash Command Leads to ... Andrew Church
• 2026/02/02 Re: Execution of subsequent commands after a command crashes. Robert Elz
• 2026/02/02 Re: Execution of subsequent commands after a command crashes. 王伟
• 2026/02/02 Re: Commentary on: Bash Command Leads to ... Greg Wooledge
• 2026/02/02 [bug #68003] Single completion doesn't get selected anonymous
• 2026/02/02 Re: Commentary on: Bash Command Leads to ... Stan Marsh
• 2026/02/02 Re: Commentary on: Bash Command Leads to ... Chet Ramey
• 2026/02/02 Re: Execution of subsequent commands after a command crashes. Andreas Kähäri
• 2026/02/02 Execution of subsequent commands after a command crashes. 王伟
• 2026/01/31 Commentary on: Bash Command Leads to ... Stan Marsh
• 2026/01/31 Re: Bash Command Leads to CLI No Longer Drawing Commands Martin D Kealey
• 2026/01/27 Re: man history correction Chet Ramey
• 2026/01/26 Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
• 2026/01/26 Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
• 2026/01/26 Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
• 2026/01/26 Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Chet Ramey
• 2026/01/26 Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Robert Elz
• 2026/01/26 Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Jari Aalto
• 2026/01/24 [bug #67957] Syntax error messages permanently change after interrupting process/command substitution parsing anonymous
• 2026/01/24 Re: Typo in Bash Reference Manual Chet Ramey
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Robert Elz
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Kähäri
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Robert Elz
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Schwab
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Denys Vlasenko
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Martin D Kealey
• 2026/01/24 Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Kähäri
• 2026/01/23 "echo $((0x))" is accepted, treated as 0x0 Denys Vlasenko
• 2026/01/23 Re: ${ ...; } can end up closing user fds open within Chet Ramey
• 2026/01/23 bash src mirror at https://github.com/bminor/bash.git gone? Cedric Blancher
• 2026/01/23 Re: bash src mirror at https://github.com/bminor/bash.git gone? Andreas Schwab
• 2026/01/23 Re: bash src mirror at https://github.com/bminor/bash.git gone? Oğuz
• 2026/01/23 Re: bash src mirror at https://github.com/bminor/bash.git gone? Cedric Blancher
• 2026/01/23 Re: bash src mirror at https://github.com/bminor/bash.git gone? Koichi Murase
• 2026/01/23 ${ ...; } can end up closing user fds open within Stephane Chazelas
• 2026/01/22 man history correction Martin F.
• 2026/01/20 Re: history -r should print error message if file doesn't exist Chet Ramey
• 2026/01/19 Typo in Bash Reference Manual Bobby Jack
• 2026/01/18 Re: history -r should print error message if file doesn't exist Ángel
• 2026/01/17 [bug #67928] Typo in bash man page anonymous
• 2026/01/14 Re: history -r should print error message if file doesn't exist Stan Marsh
• 2026/01/13 Re: segfault after redefining an alias as a function Martin D Kealey
• 2026/01/13 segfault after redefining an alias as a function Jason Puschnig
• 2026/01/13 Re: segfault after redefining an alias as a function Greg Wooledge
• 2026/01/13 Re: history -r should print error message if file doesn't exist Chet Ramey
• 2026/01/13 Re: time builtin: incorrect formatting (e.g. 0m28.:00s) Chet Ramey
• 2026/01/11 Re: time builtin: incorrect formatting (e.g. 0m28.:00s) Andrew Church
• 2026/01/11 history -r should print error message if file doesn't exist Dan Jacobson
• 2026/01/09 time builtin: incorrect formatting (e.g. 0m28.:00s) Nikola Beneš
• 2026/01/09 Re: Bash 5.3: configure fix Chet Ramey
• 2026/01/08 Bash 5.3: configure fix Marc Aurèle La France
• 2026/01/08 Re: Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
• 2026/01/06 Re: Problems encountered with printing local variables in the new command substitution in bash 5.3 Greg Wooledge
• 2026/01/06 Problems encountered with printing local variables in the new command substitution in bash 5.3 王伟
• 2026/01/06 Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
• 2026/01/06 Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
• 2026/01/05 Re: Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
• 2026/01/05 Re: `wait` triggers an infinite loop when used in an EXIT trap Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2026/01/05 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2026/01/05 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2026/01/05 Re: Bash 5.3 ARRAY_EXPORT build fix Chet Ramey
• 2026/01/05 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2026/01/03 Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
• 2026/01/02 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2026/01/02 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2026/01/02 [PATCH] Fix interaction between shell history and case-in-comsub Jason Wilkes
• 2026/01/02 A Bug in History letshaveanadventure
• 2026/01/02 Re: A Bug in History Jason Wilkes
• 2026/01/02 `wait` triggers an infinite loop when used in an EXIT trap Aleksey Covacevice
• 2026/01/02 Re: Correction in documentation Anshuman Khanna
• 2026/01/02 Re: Correction in documentation Greg Wooledge
• 2026/01/02 Correction in documentation Anshuman Khanna
• 2025/12/31 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/31 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/31 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2025/12/30 Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Duncan Roe
• 2025/12/30 Re: Length gotten from references to an value of an array is always 0 Chet Ramey
• 2025/12/27 Re: Length gotten from references to an value of an array is always 0 Martin D Kealey
• 2025/12/26 Length gotten from references to an value of an array is always 0 Ore Redstone
• 2025/12/23 Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Chet Ramey
• 2025/12/23 Re: Piping wc causes error Kye Hunter
• 2025/12/23 Re: heap-use-after-free buffered_getchar() input.c:611:11 Chet Ramey
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Zachary Santer
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2025/12/23 Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
• 2025/12/23 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/23 Re: Segmentation fault after a script runs source on itself Robert Elz
• 2025/12/22 Segmentation fault after a script runs source on itself Parker Macdonald (Student)
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Robert Elz
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Zachary Santer
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2025/12/22 Re: signed integer overflow ipow() bash/expr.c:954:12 Chet Ramey
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• 2025/12/22 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/22 Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
• 2025/12/22 Question about associative array runtime assignment vs literal initialization 王伟
• 2025/12/21 Re: RFE: Echo dots option for 'read -s' Robert Elz
• 2025/12/21 Re: RFE: Echo dots option for 'read -s' Bruce Jerrick
• 2025/12/19 heap-use-after-free buffered_getchar() input.c:611:11 anushakov--- via Bug reports for the GNU Bourne Again SHell
• 2025/12/19 Re: signed integer overflow ipow() bash/expr.c:954:12 Collin Funk
• 2025/12/19 signed integer overflow ipow() bash/expr.c:954:12 anushakov--- via Bug reports for the GNU Bourne Again SHell
• 2025/12/19 Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Grisha Levit
• 2025/12/19 heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 anushakov--- via Bug reports for the GNU Bourne Again SHell
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Stan Marsh
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/19 Re: BadInstruction ansicstr() strtrans.c:147:14 Chet Ramey
• 2025/12/19 Re: vi-mode 'v' does not reset parser state after fc execution Chet Ramey
• 2025/12/19 A 'password' mode? (Was: RFE: Echo dots option for 'read -s') Stan Marsh
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Greg Wooledge
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Stan Marsh
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Chet Ramey
• 2025/12/19 Re: RFE: Echo dots option for 'read -s' Stan Marsh
• 2025/12/18 Re: RFE: Echo dots option for 'read -s' Oğuz
• 2025/12/18 BadInstruction ansicstr() strtrans.c:147:14 anushakov--- via Bug reports for the GNU Bourne Again SHell
• 2025/12/17 Re: vi-mode 'v' does not reset parser state after fc execution Chet Ramey
• 2025/12/16 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file bug-bash
• 2025/12/15 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/15 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/15 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
• 2025/12/15 Re: Piping wc causes error Chet Ramey
• 2025/12/15 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
• 2025/12/15 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
• 2025/12/15 vi-mode 'v' does not reset parser state after fc execution Stan Marsh
• 2025/12/15 vi-mode 'v' does not reset parser state after fc execution William Pursell
• 2025/12/14 Re: AI slop (Was: Feature request: blah, blah, blah...) Stan Marsh
• 2025/12/14 Re: Feature request: Make bash do NUL separation natively Greg Wooledge
• 2025/12/14 Re: Feature request: Make bash do NUL separation natively Eric Cook
• 2025/12/14 Feature request: Make bash do NUL separation natively oliver . hinck
• 2025/12/13 Re: Piping wc causes error Kye Hunter
• 2025/12/13 Re: Piping wc causes error Greg Wooledge
• 2025/12/13 Piping wc causes error Kye Hunter
• 2025/12/13 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
• 2025/12/13 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
• 2025/12/12 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Grisha Levit
• 2025/12/12 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file G. Branden Robinson
• 2025/12/12 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
• 2025/12/12 Re: Incompatibility of quoting ampersand in substitution Chet Ramey
• 2025/12/12 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
• 2025/12/11 Re: RFE: Echo dots option for 'read -s' Martin D Kealey
• 2025/12/11 Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Grisha Levit
• 2025/12/11 (strace added) fedora42: running `gawk` permanently corrupts shell FD 0/1 | cat: -: input file is output file bug-bash

• Earlier messages