bug-bash  

Messages by Thread

• Airing dirty laundry on a technical mailing list Stan Marsh
• trap and BASH_COMMAND Mike Jonkmans
  • Re: trap and BASH_COMMAND Robert Elz
• 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: [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
• [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 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 Koichi Murase
  • Re: Project management in Savannah Collin Funk
  • Re: Project management in Savannah Chet Ramey
  • Re: Project management in Savannah 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 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
• 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 ¹, ² & ³ Grisha Levit
  • 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
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Oğuz
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Chet Ramey
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Martin D Kealey
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Maria
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Oğuz
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Chet Ramey
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Martin D Kealey
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Chris Elvidge
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Stan Marsh
  • Re: Bash exits with "Broken pipe" with process subsitution and sleep Chet Ramey
• patch: (re)enable #ifdef processing within builtin help text Martin D Kealey
• A BUG in bash-5.3 and extglob pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A BUG in bash-5.3 and extglob Greg Wooledge
  • Re: A BUG in bash-5.3 and extglob pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A BUG in bash-5.3 and extglob Greg Wooledge
  • Re: A BUG in bash-5.3 and extglob Chet Ramey
  • Re: A BUG in bash-5.3 and extglob pourko--- via Bug reports for the GNU Bourne Again SHell
  • Re: A BUG in bash-5.3 and extglob Stan Marsh
  • Re: A BUG in bash-5.3 and extglob Andreas Kähäri
  • Re: A BUG in bash-5.3 and extglob Andreas Schwab
  • Re: A BUG in bash-5.3 and extglob Greg Wooledge
  • Re: A BUG in bash-5.3 and extglob Chet Ramey
  • Re: A BUG in bash-5.3 and extglob Stan Marsh
  • Re: A BUG in bash-5.3 and extglob Chet Ramey
  • Re: A BUG in bash-5.3 and extglob Stan Marsh
  • Re: A BUG in bash-5.3 and extglob Greg Wooledge
  • Re: A BUG in bash-5.3 and extglob Lawrence Velázquez
• Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add Stan Marsh
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add Koichi Murase
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add Martin D Kealey
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add Koichi Murase
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add Martin D Kealey
• Why does setting the " LD_LIBRARY_PATH" also sets the environment variable on Linux? Yuri
  • Re: Why does setting the " LD_LIBRARY_PATH" also sets the environment variable on Linux? Andreas Schwab
  • Re: Why does setting the " LD_LIBRARY_PATH" also sets the environment variable on Linux? Robert Elz
• [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Martin Schulte
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Oğuz
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Martin Schulte
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Oğuz
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Oğuz
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Oğuz
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Koichi Murase
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Koichi Murase
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Koichi Murase
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Kevin Pulo
  • [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Kevin Pulo
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Koichi Murase
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Chet Ramey
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Martin D Kealey
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Koichi Murase
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Kevin Pulo
  • Re: [PATCH] command substitution with trailing newlines (was Re: [PATCH] Add shopts for ...) Chet Ramey
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Martin D Kealey
  • Re: [PATCH] Add shopts for trailing newlines in command substitution and here strings Koichi Murase
• monitor mode (set -m), fork optimisation and background jobs Daniel Villeneuve
  • Re: monitor mode (set -m), fork optimisation and background jobs Grisha Levit
  • Re: monitor mode (set -m), fork optimisation and background jobs Chet Ramey
• [PATCH] doc: missing parameter expansion operators in bash(1) Connor Wilkins
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Zachary Santer
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Zachary Santer
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Zachary Santer
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Connor Wilkins
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Connor Wilkins
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Zachary Santer
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Connor Wilkins
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Zachary Santer
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Duncan Roe
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Koichi Murase
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Connor Wilkins
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Eric Pruitt
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Lawrence Velázquez
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Greg Wooledge
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Eric Pruitt
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Stan Marsh
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Martin D Kealey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Chet Ramey
  • Re: [PATCH] doc: missing parameter expansion operators in bash(1) Stan Marsh
• [PATCH] isearch: printable ctrl chars in search string Grisha Levit
  • Re: [PATCH] isearch: printable ctrl chars in search string Chet Ramey
• example of monitor mode (set -m) not honoured on last command Daniel Villeneuve
  • Re: example of monitor mode (set -m) not honoured on last command Daniel Villeneuve
  • Re: example of monitor mode (set -m) not honoured on last command Grisha Levit
• Time to retire archaic mis-use of grave accent as opening single quote? Martin D Kealey
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Oğuz
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Sam James
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Collin Funk
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Sam James
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Lawrence Velázquez
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? G. Branden Robinson
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Martin D Kealey
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Chet Ramey
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Collin Funk
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Chet Ramey
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Collin Funk
  • Re: Time to retire archaic mis-use of grave accent as opening single quote? Chet Ramey
• Stray configure~ file added to git repo Keith Thompson
  • Re: Stray configure~ file added to git repo Zachary Santer
  • Re: Stray configure~ file added to git repo Greg Wooledge
  • Re: Stray configure~ file added to git repo Andreas Kähäri
  • Re: Stray configure~ file added to git repo Chet Ramey
  • Re: Stray configure~ file added to git repo Chet Ramey
• Info document incorrectly(?) says the man page is definitive Keith Thompson
• Bad filename tab completion with bracket and dollar sign Aaron Laws
  • Re: Bad filename tab completion with bracket and dollar sign Chet Ramey
• Ctrl + R, then Ctrl + C seg fault penguin p
  • Re: Ctrl + R, then Ctrl + C seg fault Grisha Levit
  • Re: Ctrl + R, then Ctrl + C seg fault Grisha Levit
  • Re: Ctrl + R, then Ctrl + C seg fault penguin p
  • Re: Ctrl + R, then Ctrl + C seg fault Grisha Levit
  • Re: Ctrl + R, then Ctrl + C seg fault penguin p
  • Re: Ctrl + R, then Ctrl + C seg fault Grisha Levit

• Earlier messages