bug-bash  

Messages by Thread

• • Re: Why does case-pattern undergo "process substitution"? Chet Ramey
• Bash History Behavior Suggestion support
  • Re: Bash History Behavior Suggestion Greg Wooledge
  • Re: Bash History Behavior Suggestion Martin D Kealey
  • Re: Bash History Behavior Suggestion Martin D Kealey
  • Re: Bash History Behavior Suggestion support
  • Re: Bash History Behavior Suggestion Lawrence Velázquez
  • Re: Bash History Behavior Suggestion support
  • Re: Bash History Behavior Suggestion Martin D Kealey
  • Re: Bash History Behavior Suggestion support
  • Re: Bash History Behavior Suggestion Martin D Kealey
  • Re: Bash History Behavior Suggestion support
  • Re: Bash History Behavior Suggestion Chet Ramey
  • Re: Bash History Behavior Suggestion Chet Ramey
• [PATCH] bash_source_fullpath: add to reset_shopt_options Grisha Levit
  • Re: [PATCH] bash_source_fullpath: add to reset_shopt_options Chet Ramey
• please make the commit log clean shynur .
  • Re: please make the commit log clean Martin D Kealey
  • Re: please make the commit log clean Koichi Murase
  • Re: please make the commit log clean Koichi Murase
  • Re: please make the commit log clean Oğuz
  • Re: please make the commit log clean shynur .
  • Re: please make the commit log clean Chet Ramey
• [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Milana
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Robert Elz
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Ángel
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Chet Ramey
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Grisha Levit
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Chet Ramey
  • Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode Robert Elz
• $@ in function gives error freek--- via Bug reports for the GNU Bourne Again SHell
  • Re: $@ in function gives error Lawrence Velázquez
  • Re: $@ in function gives error Lawrence Velázquez
  • Re: $@ in function gives error Freek de Kruijf
  • Re: $@ in function gives error alex xmb sw ratchev
  • Re: $@ in function gives error Greg Wooledge
  • Re: $@ in function gives error Lawrence Velázquez
  • Re: $@ in function gives error Greg Wooledge
  • Re: $@ in function gives error alex xmb sw ratchev
• shopt compat Martin Kealey
  • Re: shopt compat Chet Ramey
• Another redisplay issue in single-byte locales Grisha Levit
  • Re: Another redisplay issue in single-byte locales Chet Ramey
• Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ alex xmb sw ratchev
  • Re: Question on $@ vs $@$@ Greg Wooledge
  • Re: Question on $@ vs $@$@ Marc Chantreux
  • Re: Question on $@ vs $@$@ Greg Wooledge
  • Re: Question on $@ vs $@$@ Marc Chantreux
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Oğuz
  • Re: Question on $@ vs $@$@ Greg Wooledge
  • Re: Question on $@ vs $@$@ Oğuz
  • Re: Question on $@ vs $@$@ Chet Ramey
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Greg Wooledge
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Chet Ramey
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Chet Ramey
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Chet Ramey
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Lawrence Velázquez
  • Re: Question on $@ vs $@$@ Lawrence Velázquez
  • Re: Question on $@ vs $@$@ Chet Ramey
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ Robert Elz
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
  • Re: Question on $@ vs $@$@ alex xmb sw ratchev
  • Re: Question on $@ vs $@$@ Steffen Nurpmeso
• [PATCH] read: unsigned char delim issues Grisha Levit
  • Re: [PATCH] read: unsigned char delim issues Chet Ramey
• termios.h not included if sys/ioctl.h provides struct winsize Grisha Levit
  • Re: termios.h not included if sys/ioctl.h provides struct winsize Chet Ramey
• printf inconsistent results for %.0f Laur Aliste
  • Re: printf inconsistent results for %.0f Greg Wooledge
  • Re: printf inconsistent results for %.0f Chet Ramey
  • Re: printf inconsistent results for %.0f Grisha Levit
  • Re: printf inconsistent results for %.0f Chet Ramey
  • Re: printf inconsistent results for %.0f Stephane Chazelas
  • Re: printf inconsistent results for %.0f Chet Ramey
• word selection in history expansion - !?word?% Jess M
  • Re: word selection in history expansion - !?word?% Chet Ramey
  • Re: word selection in history expansion - !?word?% Jess M
  • Re: word selection in history expansion - !?word?% Chet Ramey
• Incorrect positioning when long prompt contains ANSI escape sequences + UTF-8 LANG Gioele Barabucci
  • Re: Incorrect positioning when long prompt contains ANSI escape sequences + UTF-8 LANG Martin D Kealey
  • Re: Incorrect positioning when long prompt contains ANSI escape sequences + UTF-8 LANG Gioele Barabucci
  • Re: Incorrect positioning when long prompt contains ANSI escape sequences + UTF-8 LANG Chet Ramey
• Prompt color reset after using arrow keys Gioele Barabucci
  • Re: Prompt color reset after using arrow keys Chet Ramey
• whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Grisha Levit
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Greg Wooledge
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Chet Ramey
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Chet Ramey
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Martin D Kealey
  • Re: whats wrong , exit code 11 on android termux Martin D Kealey
  • Re: whats wrong , exit code 11 on android termux Oğuz
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Chet Ramey
  • Re: whats wrong , exit code 11 on android termux alex xmb sw ratchev
  • Re: whats wrong , exit code 11 on android termux Eric Pruitt
  • Re: whats wrong , exit code 11 on android termux Chris Elvidge
  • Re: whats wrong , exit code 11 on android termux Chet Ramey
• Potentially misleading documentation of SECONDS variable Bash-help via Bug reports for the GNU Bourne Again SHell
  • Re: Potentially misleading documentation of SECONDS variable alex xmb sw ratchev
  • Re: Potentially misleading documentation of SECONDS variable Koichi Murase
  • Re: Potentially misleading documentation of SECONDS variable alex xmb sw ratchev
  • Re: Potentially misleading documentation of SECONDS variable bash
  • Re: Potentially misleading documentation of SECONDS variable Chet Ramey
  • Re: Potentially misleading documentation of SECONDS variable G. Branden Robinson
  • Re: Potentially misleading documentation of SECONDS variable Chet Ramey
  • Re: Potentially misleading documentation of SECONDS variable felix
  • Re: Potentially misleading documentation of SECONDS variable Martin D Kealey
  • Re: Potentially misleading documentation of SECONDS variable Chet Ramey
  • Re: Potentially misleading documentation of SECONDS variable bash
  • Re: Potentially misleading documentation of SECONDS variable Ángel
• [bug #66068] built-in printf function not working with float anonymous
  • Re: [bug #66068] built-in printf function not working with float Greg Wooledge
  • Re: [bug #66068] built-in printf function not working with float Chet Ramey
• return from trap while reading with readline breaks completion Oğuz
  • Re: return from trap while reading with readline breaks completion Chet Ramey
• shell-expand-line working strangely without shebangs Jae Juang
  • Re: shell-expand-line working strangely without shebangs Chet Ramey
  • Re: shell-expand-line working strangely without shebangs Jae Juang
  • Re: shell-expand-line working strangely without shebangs Chet Ramey
• Bash-5.2 Patch 32 Chet Ramey
• Bash-5.2 Patch 31 Chet Ramey
• Bash-5.2 Patch 30 Chet Ramey
• Bash-5.2 Patch 29 Chet Ramey
• Bash-5.2 Patch 28 Chet Ramey
• Bash-5.2 Patch 27 Chet Ramey
• Bogus (intptr_t) casts Martin D Kealey
  • Re: Bogus (intptr_t) casts Dale R. Worley
  • Re: Bogus (intptr_t) casts Chet Ramey
  • Re: Bogus (intptr_t) casts Martin D Kealey
  • Re: Bogus (intptr_t) casts Chet Ramey
• Backticked, nested command will steal piped stdin Justus
  • Re: Backticked, nested command will steal piped stdin Dale R. Worley
  • Re: Backticked, nested command will steal piped stdin Greg Wooledge
  • Re: Backticked, nested command will steal piped stdin Chet Ramey
• if source command.sh & set -e issue Mor Shalev via Bug reports for the GNU Bourne Again SHell
  • Re: if source command.sh & set -e issue Greg Wooledge
  • Re: if source command.sh & set -e issue Mor Shalev via Bug reports for the GNU Bourne Again SHell
  • Re: if source command.sh & set -e issue Mor Shalev via Bug reports for the GNU Bourne Again SHell
  • Re: if source command.sh & set -e issue Greg Wooledge
  • Re: if source command.sh & set -e issue Martin D Kealey
  • Re: if source command.sh & set -e issue Chet Ramey
  • Re: if source command.sh & set -e issue Chet Ramey
  • a groff convenience for quoting man pages (was: if source command.sh & set -e issue) G. Branden Robinson
• improving '{...}' in bash? Harald Dunkel
  • Re: improving '{...}' in bash? Martin D Kealey
  • Re: improving '{...}' in bash? Harald Dunkel
  • Re: improving '{...}' in bash? felix
• [PATCH] malloc: fix out-of-bounds read Collin Funk
  • Re: [PATCH] malloc: fix out-of-bounds read Chet Ramey
  • Re: [PATCH] malloc: fix out-of-bounds read Collin Funk
  • Re: [PATCH] malloc: fix out-of-bounds read Chet Ramey
• [Bug] Array declaration only includes first element Charles Dong via Bug reports for the GNU Bourne Again SHell
  • Re: [Bug] Array declaration only includes first element Greg Wooledge
  • Re: [Bug] Array declaration only includes first element Lawrence Velázquez
• Strange behavior after removing folder Батунин Сергей
  • Re: Strange behavior after removing folder Chet Ramey
• Error in "help ulimit": missing unit info Carlo Teubner
  • Re: Error in "help ulimit": missing unit info Chet Ramey
• [bug #65981] "bash test -v" does not work as documented with "export KEY=" anonymous
  • Re: [bug #65981] "bash test -v" does not work as documented with "export KEY=" Andreas Kähäri
  • Re: [bug #65981] "bash test -v" does not work as documented with "export KEY=" Robert Elz
• pwd and prompt don't update after deleting current working directory David Hedlund
  • Re: pwd and prompt don't update after deleting current working directory Lawrence Velázquez
  • Re: pwd and prompt don't update after deleting current working directory David Hedlund
  • Re: pwd and prompt don't update after deleting current working directory Lawrence Velázquez
  • Re: pwd and prompt don't update after deleting current working directory Chet Ramey
  • Re: pwd and prompt don't update after deleting current working directory David Hedlund
  • Re: pwd and prompt don't update after deleting current working directory Chet Ramey
  • Re: pwd and prompt don't update after deleting current working directory felix
  • Re: pwd and prompt don't update after deleting current working directory Lawrence Velázquez
  • Re: pwd and prompt don't update after deleting current working directory David Hedlund
  • Re: pwd and prompt don't update after deleting current working directory Martin D Kealey

• Earlier messages
• Later messages