bug-bash  

Messages by Thread

• • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chris Elvidge
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chet Ramey
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Robert Elz
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chet Ramey
  • [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Stan Marsh
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chris Elvidge
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Martin Schulte
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chris Elvidge
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Phi Debian
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Lawrence Velázquez
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chet Ramey
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Lawrence Velázquez
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Chet Ramey
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Stan Marsh
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Stan Marsh
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Phi Debian
  • Re: [PATCH] examples/s-f/Bash_aliases: Fix off-by-one error Stan Marsh
• builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Andreas Kähäri
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help Andreas Kähäri
  • Re: builtin_name --help Andreas Kähäri
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help Andreas Kähäri
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help Lawrence Velázquez
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Chet Ramey
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: builtin_name --help Andreas Kähäri
  • Re: builtin_name --help pourko--- via Bug reports for the GNU Bourne Again SHell
• bash hangs when executing a script with a here document larger than 64 KiB Bruno Haible via Bug reports for the GNU Bourne Again SHell
  • Re: bash hangs when executing a script with a here document larger than 64 KiB Chet Ramey
• CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command Chet Ramey
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command Greg Wooledge
  • Re: CORRECTED: Bug in the read command Chet Ramey
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command Chet Ramey
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command Chet Ramey
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command Chet Ramey
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: CORRECTED: Bug in the read command pourko2--- via Bug reports for the GNU Bourne Again SHell
• Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Andreas Kähäri
  • Re: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Greg Wooledge
  • Re: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Greg Wooledge
  • Re: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Chet Ramey
  • Re: Bug in the read command Robert Elz
  • Re: Bug in the read command Greg Wooledge
  • Re: Bug in the read command Andreas Schwab
  • Re: Bug in the read command Robert Elz
  • Re: Bug in the read command Chet Ramey
  • Re: Bug in the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bug in the read command Chet Ramey
  • Re: Bug in the read command Oğuz
  • Re: Bug in the read command Chet Ramey
  • Re: Bug in the read command Robert Elz
  • Re: Bug in the read command Chet Ramey
  • Re: Bug in the read command Greg Wooledge
• A problem with the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A problem with the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A problem with the read command Sam James
  • Re: A problem with the read command pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A problem with the read command Stan Marsh
• [PATCH] ansic_quote: zero mbstate when needed Grisha Levit
  • Re: [PATCH] ansic_quote: zero mbstate when needed Chet Ramey
• [meta] Mostly on the social aspects of FLOSS project management G. Branden Robinson
  • Re: [meta] Mostly on the social aspects of FLOSS project management Oğuz
• Re: [bug #67486] Can't use if with two separate awk floating number ... Stan Marsh
  • Re: [bug #67486] Can't use if with two separate awk floating number ... Phi Debian
  • Re: [bug #67486] Can't use if with two separate awk floating number ... Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: [bug #67486] Can't use if with two separate awk floating number ... Greg Wooledge
  • Re: [bug #67486] Can't use if with two separate awk floating number ... Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number ... Lawrence Velázquez
• Airing dirty laundry on a technical mailing list Stan Marsh
• trap and BASH_COMMAND Mike Jonkmans
  • Re: trap and BASH_COMMAND Robert Elz
  • Re: trap and BASH_COMMAND Chet Ramey
  • Re: trap and BASH_COMMAND Mike Jonkmans
  • Re: trap and BASH_COMMAND Chet Ramey
  • Re: trap and BASH_COMMAND Mike Jonkmans
• Missing semicolon tolerated after double-bracket [[ ]] expression Martin Jambon
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Koichi Murase
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Greg Wooledge
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Greg Wooledge
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Robert Elz
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Robert Elz
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Martin D Kealey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Greg Wooledge
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Robert Elz
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Greg Wooledge
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Oğuz
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Andreas Schwab
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Collin Funk
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Martin D Kealey
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Lawrence Velázquez
  • Re: Missing semicolon tolerated after double-bracket [[ ]] expression Chet Ramey
• [bug #67486] Can't use if with two separate awk floating number comparisons anonymous
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Oğuz
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Koichi Murase
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Martin D Kealey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons G. Branden Robinson
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Martin D Kealey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • On Martin D. Kealey (was: [bug #67486] Can't use if with two separate awk floating number comparisons) G. Branden Robinson
  • Re: On Martin D. Kealey (was: [bug #67486] Can't use if with two separate awk floating number comparisons) Koichi Murase
  • Re: On Martin D. Kealey Chet Ramey
  • Re: On Martin D. Kealey Collin Funk
  • Re: On Martin D. Kealey (was: [bug #67486] Can't use if with two separate awk floating number comparisons) Greg Wooledge
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Koichi Murase
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons G. Branden Robinson
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Chet Ramey
  • Re: [bug #67486] Can't use if with two separate awk floating number comparisons Koichi Murase
  • Project management in Savannah (was: [bug #67486] Can't use if with two separate awk floating number comparisons) G. Branden Robinson
  • Re: Project management in Savannah Collin Funk
  • Re: Project management in Savannah Chet Ramey
  • Re: Project management in Savannah Chet Ramey
• Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Greg Wooledge
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Lawrence Velázquez
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Chet Ramey
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Grisha Levit
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Grisha Levit
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Greg Wooledge
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Chet Ramey
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Grisha Levit
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Chet Ramey
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Oğuz
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Duncan Roe via Bug reports for the GNU Bourne Again SHell
  • Re: Bash glob range [0-5] in UTF-8 locale misses ¹, ² & ³ Oğuz
• A question about the bash loadables pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A question about the bash loadables Chet Ramey
  • Re: A question about the bash loadables Michael via Bug reports for the GNU Bourne Again SHell
  • Re: A question about the bash loadables pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A question about the bash loadables Stan Marsh
  • Re: A question about the bash loadables pourko--- via Bug reports for the GNU Bourne Again SHell
• [bug #67473] ":|eval (exit 42)" does not return 42 Philipp Hahn
• [PATCH] tests: avoid user's startup and history files Grisha Levit
  • Re: [PATCH] tests: avoid user's startup and history files Chet Ramey
• Bash exits with "Broken pipe" with process subsitution and sleep Maria
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Andreas Schwab
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Maria
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep G. Branden Robinson
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Maria
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Andreas Schwab
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Andreas Schwab
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Maria
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Andreas Schwab
  • Bash exits with "Broken pipe" with process subsitution and sleep Oğuz
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Martin D Kealey

• Earlier messages
• Later messages