bug-bash  

Messages by Thread

• • Re: Parsing regression with for loop in case statement Chet Ramey
• echo test >& "quote'test" squeaky
  • Re: echo test >& "quote'test" Greg Wooledge
  • Re: echo test >& "quote'test" Chet Ramey
• strtoimax test still broken Dag-Erling Smørgrav
  • Re: strtoimax test still broken Chet Ramey
  • Re: strtoimax test still broken Dag-Erling Smørgrav
  • Re: strtoimax test still broken Chet Ramey
• Potential Bash Script Vulnerability admin
  • Re: Potential Bash Script Vulnerability Jon Seymour
  • Re: Potential Bash Script Vulnerability Kerin Millar
  • Re: Potential Bash Script Vulnerability admin
  • Re: Potential Bash Script Vulnerability Greg Wooledge
  • Re: Potential Bash Script Vulnerability Kerin Millar
  • Re: Potential Bash Script Vulnerability Robert Elz
  • Re: Potential Bash Script Vulnerability John Passaro
  • Re: Potential Bash Script Vulnerability Kerin Millar
  • Re: Potential Bash Script Vulnerability Robert Elz
  • Re: Potential Bash Script Vulnerability Greg Wooledge
  • Re: Potential Bash Script Vulnerability admin
  • Re: Potential Bash Script Vulnerability Greg Wooledge
  • Re: Potential Bash Script Vulnerability Andreas Schwab
  • Re: Potential Bash Script Vulnerability admin
  • Re: Potential Bash Script Vulnerability Oğuz
  • Re: Potential Bash Script Vulnerability Robert Elz
  • Re: Potential Bash Script Vulnerability Oğuz
  • Re: Potential Bash Script Vulnerability Robert Elz
  • Re: Potential Bash Script Vulnerability Oğuz
  • Re: Potential Bash Script Vulnerability Martin D Kealey
  • Re: Potential Bash Script Vulnerability Kerin Millar
  • Re: Potential Bash Script Vulnerability Martin D Kealey
  • Re: Potential Bash Script Vulnerability Chet Ramey
• Bug#306043: bash executable completion doesn't work if there is a space in the executable path Gioele Barabucci
• [sr #111047] Value of BASHPID changes when inside a here-document Richard Waite
  • Re: [sr #111047] Value of BASHPID changes when inside a here-document Lawrence Velázquez
  • Re: [sr #111047] Value of BASHPID changes when inside a here-document Chet Ramey
• Document ulimit's "unlimited" limit in manual page Martin Guy
  • Re: Document ulimit's "unlimited" limit in manual page Martin Guy
• Scope change in loops with "read" built-in Linde, Evan
  • Re: Scope change in loops with "read" built-in Greg Wooledge
  • RE: Scope change in loops with "read" built-in Linde, Evan
  • Re: Scope change in loops with "read" built-in Dale R. Worley
  • Re: Scope change in loops with "read" built-in Kerin Millar
  • Re: Scope change in loops with "read" built-in Greg Wooledge
• Re: Manual: clarify what POSIX stands for Martin D Kealey
  • Re: Manual: clarify what POSIX stands for Poor Yorick
  • Re: Manual: clarify what POSIX stands for Lawrence Velázquez
  • Re: Manual: clarify what POSIX stands for Chet Ramey
• Bug tracking Martin D Kealey
  • Re: Bug tracking Oğuz
  • Re: Bug tracking Koichi Murase
  • Re: Bug tracking Chet Ramey
  • Re: Bug tracking Chet Ramey
  • Re: Bug tracking Martin D Kealey
• > /dev/stderr 2>&- Reuben
  • Re: > /dev/stderr 2>&- Greg Wooledge
  • Re: > /dev/stderr 2>&- Chet Ramey
• install-headers stdckdint.h error Grisha Levit
  • Re: install-headers stdckdint.h error Chet Ramey
  • Re: install-headers stdckdint.h error Grisha Levit
• [PATCH 13/13] doc/bash.1: Trivially refactor *roff markup. G. Branden Robinson
• [PATCH 11/13] [man pages]: Make comment more informative. G. Branden Robinson
• [PATCH 12/13] doc/bash.1: Fix *roff style nit. G. Branden Robinson
  • Re: [PATCH 12/13] doc/bash.1: Fix *roff style nit. Chet Ramey
• [PATCH 10/13] lib/readline/doc/history.3: Make `EX` and `EE` man(7) macros usable on DWB troff. G. Branden Robinson
• [PATCH 07/13] lib/readline/doc/history.3: Fix hyphen-minus signs. G. Branden Robinson
• [PATCH 09/13] lib/readline/doc/history.3: Revise inline struct. G. Branden Robinson
• [PATCH 04/13] lib/readline/doc/history.3: Replace blank lines with macro calls. G. Branden Robinson
• [PATCH 08/13] lib/readline/doc/history.3: Fix font thinko. G. Branden Robinson
• [PATCH 05/13] lib/readline/doc/history.3: Fix style minutia. G. Branden Robinson
• [PATCH 06/13] lib/readline/doc/history.3: Drop microtypography. G. Branden Robinson
  • Re: [PATCH 06/13] lib/readline/doc/history.3: Drop microtypography. Chet Ramey
  • Re: [PATCH 06/13] lib/readline/doc/history.3: Drop microtypography. G. Branden Robinson
  • Re: [PATCH 06/13] lib/readline/doc/history.3: Drop microtypography. Chet Ramey
• [PATCH 01/13] lib/readline/doc/history.3: Fix failure to render on DWB and Solaris 10 troff. G. Branden Robinson
• [PATCH 03/13] lib/readline/doc/history.3: Drop spacing around (sub)section headings. G. Branden Robinson
• [PATCH 02/13] doc/bash.1: Fix groff man(7) style warnings. G. Branden Robinson
• Docco Phi Debian
  • Re: Docco Andreas Kähäri
  • Re: Docco Phi Debian
  • Re: Docco Phi Debian
  • Re: Docco Chet Ramey
  • Re: Docco Greg Wooledge
  • Re: Docco Andreas Schwab
  • Re: Docco Chet Ramey
  • Re: Docco Chet Ramey
• Memory Leak - Bash 4.3.x30 Jordi Ferrer
  • Re: Memory Leak - Bash 4.3.x30 Chet Ramey
  • Re: Memory Leak - Bash 4.3.x30 Jordi Ferrer
• funsub in PS2 Grisha Levit
  • Re: funsub in PS2 Chet Ramey
• [PATCH] fix cmd and hist nums in ${var@P} inside $PS[012] Grisha Levit
  • Re: [PATCH] fix cmd and hist nums in ${var@P} inside $PS[012] Chet Ramey
• Debian bug #929178: wrong trap displayed inside functions Gioele Barabucci
  • Debian bug #929178: wrong trap displayed inside functions Oğuz
  • Re: Debian bug #929178: wrong trap displayed inside functions Gioele Barabucci
  • Debian bug #929178: wrong trap displayed inside functions Oğuz
  • Re: Debian bug #929178: wrong trap displayed inside functions G. Branden Robinson
  • Re: Debian bug #929178: wrong trap displayed inside functions Oğuz
  • Re: Debian bug #929178: wrong trap displayed inside functions G. Branden Robinson
  • Re: Debian bug #929178: wrong trap displayed inside functions Martin D Kealey
  • Debian bug #929178: wrong trap displayed inside functions Oğuz
  • Re: Debian bug #929178: wrong trap displayed inside functions Gioele Barabucci
  • Re: Debian bug #929178: wrong trap displayed inside functions Chet Ramey
  • Re: Debian bug #929178: wrong trap displayed inside functions Chet Ramey
• Add option to just print history, with no added timestamps or line numbers Dan Jacobson
  • Re: Add option to just print history, with no added timestamps or line numbers Lawrence Velázquez
  • Re: Add option to just print history, with no added timestamps or line numbers Martin D Kealey
  • Re: Add option to just print history, with no added timestamps or line numbers Dan Jacobson
  • Re: Add option to just print history, with no added timestamps or line numbers Lawrence Velázquez
  • Re: Add option to just print history, with no added timestamps or line numbers Dan Jacobson
  • Re: Add option to just print history, with no added timestamps or line numbers Lawrence Velázquez
  • Re: Add option to just print history, with no added timestamps or line numbers Dan Jacobson
  • Re: Add option to just print history, with no added timestamps or line numbers Chet Ramey
  • Re: Add option to just print history, with no added timestamps or line numbers Dan Jacobson
• History Expansion in Arithmetic Expansion A4-Tacks
  • Re: History Expansion in Arithmetic Expansion alex xmb sw ratchev
  • Re: History Expansion in Arithmetic Expansion A4-Tacks
  • Re: History Expansion in Arithmetic Expansion Lawrence Velázquez
  • Re: History Expansion in Arithmetic Expansion Zachary Santer
• feat: exit 1 "file not found" teknopaul
  • Re: feat: exit 1 "file not found" Dale R. Worley
  • Re: feat: exit 1 "file not found" Chet Ramey
• Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Gioele Barabucci
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Oğuz
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Gioele Barabucci
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Chet Ramey
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Gioele Barabucci
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Chet Ramey
  • Re: Debian bug #822605: SIGPIPE not handled in "echo >", terminates shell Chet Ramey
• "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Zachary Santer
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Zachary Santer
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Lawrence Velázquez
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Zachary Santer
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax alex xmb sw ratchev
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Léa Gris
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax alex xmb sw ratchev
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Lawrence Velázquez
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Zachary Santer
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Chet Ramey
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Lawrence Velázquez
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Zachary Santer
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Oğuz
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Oğuz
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Oğuz
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Lawrence Velázquez
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Dennis Williamson
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Greg Wooledge
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Dennis Williamson
  • Re: "${assoc[@]@k}" doesn't get expanded to separate words within compound assignment syntax Chet Ramey
• Small typo in bash man-page nasm--- via Bug reports for the GNU Bourne Again SHell
  • Re: Small typo in bash man-page Chet Ramey
• Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi tpeplt
  • Re: Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi Oğuz
  • Re: Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi Kerin Millar
  • Re: Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi Lawrence Velázquez
  • Re: Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi Chet Ramey
  • Re: Bash 5.2: Missing ‘shopt’ option ‘syslog_history’ in doc/bashref.texi tpeplt
• Documentation Bug: ‘of’ should be ‘or’ Abigail Read
  • Re: Documentation Bug: ‘of’ should be ‘or’ alex xmb sw ratchev
  • Re: Documentation Bug: ‘of’ should be ‘or’ Chet Ramey
• Incorrect handling of echo in POSIX mode Clint Hepner
  • Re: Incorrect handling of echo in POSIX mode Chet Ramey
  • Re: Incorrect handling of echo in POSIX mode Robert Elz
• Bash printf should diagnose integer overflow Paul Eggert
  • Re: Bash printf should diagnose integer overflow Chet Ramey
  • Re: Bash printf should diagnose integer overflow Paul Eggert
  • Re: Bash printf should diagnose integer overflow Chet Ramey
  • Re: Bash printf should diagnose integer overflow alex xmb sw ratchev
  • Re: Bash printf should diagnose integer overflow Paul Eggert
  • Re: Bash printf should diagnose integer overflow Chet Ramey
  • Re: Bash printf should diagnose integer overflow Chet Ramey
  • Re: Bash printf should diagnose integer overflow Paul Eggert
  • Re: Bash printf should diagnose integer overflow Chet Ramey
  • Re: Bash printf should diagnose integer overflow Paul Eggert
  • Re: Bash printf should diagnose integer overflow Chet Ramey
• Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Carl Edquist
  • Re: Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? Carl Edquist via Bug reports for the GNU Bourne Again SHell
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? felix
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Chet Ramey
  • Re: Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Zachary Santer
  • Re: Examples of concurrent coproc usage? Carl Edquist
  • Re: Examples of concurrent coproc usage? Andreas Schwab
  • Re: Examples of concurrent coproc usage? Zachary Santer

• Earlier messages
• Later messages