bug-bash  

Messages by Thread

• • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Oğuz
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments #!microsuxx
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Zachary Santer
  • Re: 'wait -n' with and without id arguments Grisha Levit
  • posix vs default mode nonsense Zachary Santer
  • Re: posix vs default mode nonsense Chet Ramey
  • Re: posix vs default mode nonsense Zachary Santer
  • Re: posix vs default mode nonsense Lawrence Velázquez
  • Re: posix vs default mode nonsense Zachary Santer
  • Re: posix vs default mode nonsense Chet Ramey
  • Re: posix vs default mode nonsense Zachary Santer
  • Re: posix vs default mode nonsense Chet Ramey
  • Re: posix vs default mode nonsense Robert Elz
  • Re: posix vs default mode nonsense Chet Ramey
  • Re: 'wait -n' with and without id arguments Lawrence Velázquez
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Chet Ramey
  • Re: 'wait -n' with and without id arguments Robert Elz
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions alex xmb sw ratchev
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions alex xmb sw ratchev
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions Zachary Santer
  • ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Lawrence Velázquez
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Chet Ramey
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Greg Wooledge
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Martin D Kealey
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Chet Ramey
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Lawrence Velázquez
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active microsuxxor
  • Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Robert Elz
  • Re: waiting for process substitutions Greg Wooledge
  • Re: waiting for process substitutions Oğuz
  • Re: waiting for process substitutions Martin D Kealey
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Martin D Kealey
  • Re: waiting for process substitutions Zachary Santer
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions Greg Wooledge
  • Re: waiting for process substitutions Dale R. Worley
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions alex xmb sw ratchev
  • Re: waiting for process substitutions Chet Ramey
  • Re: waiting for process substitutions alex xmb sw ratchev
  • Re: waiting for process substitutions Greg Wooledge
  • Re: waiting for process substitutions alex xmb sw ratchev
  • Re: waiting for process substitutions Dale R. Worley
• --rcfile and non existing files Gioele Barabucci
  • Re: --rcfile and non existing files Chet Ramey
  • Re: --rcfile and non existing files Robert Elz
• use-after-free in set -o vi mode rtm
  • Re: use-after-free in set -o vi mode Chet Ramey
• function names starting with % Oğuz
  • Re: function names starting with % Zachary Santer
  • Re: function names starting with % Emanuele Torre
  • Re: function names starting with % Oğuz
  • Re: function names starting with % Chet Ramey
• readarray leaves a NULL char embedded in each element Rob Gardner
  • Re: readarray leaves a NULL char embedded in each element Davide Brini
  • Re: readarray leaves a NULL char embedded in each element Davide Brini
  • Re: readarray leaves a NULL char embedded in each element Greg Wooledge
  • Re: readarray leaves a NULL char embedded in each element Greg Wooledge
• Proposal for a New Bash Option: failfast for Immediate Pipeline Failure ama bamo
  • Re: Proposal for a New Bash Option: failfast for Immediate Pipeline Failure Martin D Kealey
  • Re: Proposal for a New Bash Option: failfast for Immediate Pipeline Failure Zachary Santer
  • Re: Proposal for a New Bash Option: failfast for Immediate Pipeline Failure Chet Ramey
  • Re: Proposal for a New Bash Option: failfast for Immediate Pipeline Failure ama bamo
• printf, binary data, leading single quote and non ASCII codesets Gioele Barabucci
  • Re: printf, binary data, leading single quote and non ASCII codesets Oğuz
  • Re: printf, binary data, leading single quote and non ASCII codesets alex xmb sw ratchev
  • Re: printf, binary data, leading single quote and non ASCII codesets Chet Ramey
• STRTOLD_BROKEN test fails with gcc14 af
  • Re: STRTOLD_BROKEN test fails with gcc14 Chet Ramey
• history-search-backward clobbers history Andreas Schwab
  • Re: history-search-backward clobbers history Chet Ramey
  • Re: history-search-backward clobbers history Andreas Schwab
  • Re: history-search-backward clobbers history Chet Ramey
  • Re: history-search-backward clobbers history Andreas Schwab
  • Re: history-search-backward clobbers history Chet Ramey
  • Re: history-search-backward clobbers history Andreas Schwab
  • Re: history-search-backward clobbers history Chet Ramey
• bash crashes when splitcurl script try download non existent file Mikhail Gavrilov
  • Re: bash crashes when splitcurl script try download non existent file Chet Ramey
  • Re: bash crashes when splitcurl script try download non existent file Mikhail Gavrilov
  • Re: bash crashes when splitcurl script try download non existent file Chet Ramey
  • Re: bash crashes when splitcurl script try download non existent file Greg Wooledge
• DEBUG trap in a background shell steals controlling terminal forcing parent shell to exit Mark March
  • Re: DEBUG trap in a background shell steals controlling terminal forcing parent shell to exit Mark March
  • Re: DEBUG trap in a background shell steals controlling terminal forcing parent shell to exit Chet Ramey
  • Re: DEBUG trap in a background shell steals controlling terminal forcing parent shell to exit Chet Ramey
  • Re: DEBUG trap in a background shell steals controlling terminal forcing parent shell to exit Mark March
• 'declare -i var=var' for var initially declared in calling scope Zachary Santer
  • Re: 'declare -i var=var' for var initially declared in calling scope Chet Ramey
• Question that baffles AI (all of them) Saint Michael
  • Re: Question that baffles AI (all of them) Lawrence Velázquez
  • Re: Question that baffles AI (all of them) alex xmb sw ratchev
  • Re: Question that baffles AI (all of them) Greg Wooledge
• Poor messages when the '#!' file isn't found Dan Jacobson
  • Re: Poor messages when the '#!' file isn't found Greg Wooledge
  • Re: Poor messages when the '#!' file isn't found Martin D Kealey
• set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • RE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • Re: set -a leads to truncated output from ps Oğuz
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • it, soRE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: it, soRE: set -a leads to truncated output from ps Oğuz
  • RE: it, soRE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: it, soRE: set -a leads to truncated output from ps Greg Wooledge
  • Re: it, soRE: set -a leads to truncated output from ps alex xmb sw ratchev
  • Re: it, soRE: set -a leads to truncated output from ps Robert Elz
  • Re: set -a leads to truncated output from ps Andreas Schwab
  • RE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: set -a leads to truncated output from ps Chet Ramey
  • Re: set -a leads to truncated output from ps Oğuz
  • RE: set -a leads to truncated output from ps Alain BROSSARD
  • Re: set -a leads to truncated output from ps Greg Wooledge
  • RE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: set -a leads to truncated output from ps Greg Wooledge
  • Re: set -a leads to truncated output from ps Koichi Murase
  • Re: set -a leads to truncated output from ps Oğuz
  • Re: set -a leads to truncated output from ps Greg Wooledge
  • Re: set -a leads to truncated output from ps Koichi Murase
  • Re: set -a leads to truncated output from ps Koichi Murase
  • Re: set -a leads to truncated output from ps Oğuz
  • Re: set -a leads to truncated output from ps Chet Ramey
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • Re: set -a leads to truncated output from ps Chet Ramey
  • Re: set -a leads to truncated output from ps alex xmb sw ratchev
  • Re: set -a leads to truncated output from ps Chet Ramey
  • Re: set -a leads to truncated output from ps Chet Ramey
  • Re: set -a leads to truncated output from ps Robert Elz
  • RE: set -a leads to truncated output from ps Alain BROSSARD via Bug reports for the GNU Bourne Again SHell
  • Re: set -a leads to truncated output from ps Robert Elz
  • Re: set -a leads to truncated output from ps Greg Wooledge
• Echoing commands Angelo Borsotti
  • Re: Echoing commands Greg Wooledge
  • Re: Echoing commands alex xmb sw ratchev

• Earlier messages
• Later messages