bug-bash  

Messages by Thread

• Bash-5.3 patch 19 Chet Ramey
• Bash-5.3 patch 20 Chet Ramey
• Bash-5.3 patch 17 Chet Ramey
• Bash-5.3 patch 16 Chet Ramey
• Readline prefix display length suppresses completion coloring Andreas Hartmann
  • Re: Readline prefix display length suppresses completion coloring Chet Ramey
• Re: Subject: NSUB & NSUB0 feature proposal Zachary Santer
  • Re: Subject: NSUB & NSUB0 feature proposal Greg Wooledge
  • Re: Subject: NSUB & NSUB0 feature proposal Chet Ramey
• Segfault on large echo -e wiebe
  • Re: Segfault on large echo -e Koichi Murase
• Bash segfault in large echo -e Wiebe Cazemier via Bug reports for the GNU Bourne Again SHell
• Re: feature proposal: expand associative arrays in lexicographic order Stan Marsh
  • Re: feature proposal: expand associative arrays in lexicographic order Koichi Murase
• [SECURITY] GNU Bash EXIT Trap Arbitrary Code Execution George Simpson via Bug reports for the GNU Bourne Again SHell
  • Fw: [SECURITY] GNU Bash EXIT Trap Arbitrary Code Execution George Simpson via Bug reports for the GNU Bourne Again SHell
  • Re: [SECURITY] GNU Bash EXIT Trap Arbitrary Code Execution Earnestly
  • Re: [SECURITY] GNU Bash EXIT Trap Arbitrary Code Execution Chet Ramey
• [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler correspondence2--- via Bug reports for the GNU Bourne Again SHell
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Paul Eggert
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Sam James
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Collin Funk
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Collin Funk
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler G. Branden Robinson
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Zachary Santer
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
  • Re: [SECURITY] Async-signal-unsafe operations in alrm_catcher() signal handler Chet Ramey
• Re: sed and awk (Was: The "asort" extension (Was: feature proposal: expand ... Stan Marsh
  • Re: sed and awk (Was: The "asort" extension (Was: feature proposal: expand ... G. Branden Robinson
  • Re: sed and awk (Was: The "asort" extension (Was: feature proposal: expand ... Wiley Young
• sed and awk (Was: The "asort" extension (Was: feature proposal: expand ...) lol) Zachary Santer
• Command saved incorrectly in history. Alberto Millán
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Alberto Millán
  • Re: Command saved incorrectly in history. Martin D Kealey
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Robert Elz
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Mike Jonkmans
  • Re: Command saved incorrectly in history. Andreas Schwab
  • Re: Command saved incorrectly in history. Mike Jonkmans
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Mike Jonkmans
  • Re: Command saved incorrectly in history. Robert Elz
  • Re: Command saved incorrectly in history. Mike Jonkmans
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Robert Elz
  • Re: Command saved incorrectly in history. Chet Ramey
  • Re: Command saved incorrectly in history. Robert Elz
  • Re: Command saved incorrectly in history. Chet Ramey
• [bug #68650] HISTFILE truncation on open disrespects timestamps Ilya
• [bug #68649] Missing space after HISTTIMEFORMAT Ilya
• [bug #68646] history -w does not reset history_lines_this_session Ilya
• The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Zachary Santer
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Greg Wooledge
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) G. Branden Robinson
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Chet Ramey
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) G. Branden Robinson
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Zachary Santer
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Chet Ramey
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Zachary Santer
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Greg Wooledge
  • The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
  • The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) G. Branden Robinson
  • The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Greg Wooledge
  • Re: The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Chet Ramey
  • The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
  • The "asort" extension (Was: feature proposal: expand associative arrays in lexicographic order ...) Stan Marsh
• [bug #68645] Confusing rules on appending to HISTFILE Ilya
  • Re: [bug #68645] Confusing rules on appending to HISTFILE Chet Ramey
• Re: feature proposal: expand associative arrays in lexicographic order ... Stan Marsh
  • Re: feature proposal: expand associative arrays in lexicographic order ... Chet Ramey
  • Re: feature proposal: expand associative arrays in lexicographic order ... Stan Marsh
• Re: [PATCH] multibyte_identifiers: opt-in UTF-8 ... Stan Marsh
• [bug #68641] history -w and -a ignore HISTFILESIZE anonymous
  • Re: [bug #68641] history -w and -a ignore HISTFILESIZE Félix Hauri via Bug reports for the GNU Bourne Again SHell
• feature proposal: expand associative arrays in lexicographic order of keys Zachary Santer
  • Re: feature proposal: expand associative arrays in lexicographic order of keys Chet Ramey
  • Re: feature proposal: expand associative arrays in lexicographic order of keys Zachary Santer
  • Re: feature proposal: expand associative arrays in lexicographic order of keys Chet Ramey
  • Re: feature proposal: expand associative arrays in lexicographic order of keys Koichi Murase
• Use of tee(2) to speedup reading from pipes Sam James
  • Re: Use of tee(2) to speedup reading from pipes Sam James
  • Re: Use of tee(2) to speedup reading from pipes Chet Ramey
• Taint marker for set -r Sam James
  • Re: Taint marker for set -r Chet Ramey
  • Re: Taint marker for set -r Sam James
  • Re: Taint marker for set -r Chet Ramey
• manual: clarify -n (noexec) vs interactive shells Tom Hale
  • Re: manual: clarify -n (noexec) vs interactive shells Chet Ramey
• Re:  (Buglet) job numbers do not get re-used (sometimes) Wiley Young
• New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Zachary Santer
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
  • Re: New word splitting semantics for kvpair compound assignment Martin D Kealey
  • Re: New word splitting semantics for kvpair compound assignment Chet Ramey
• (Buglet) job numbers do not get re-used (sometimes) Stan Marsh
  • Re: (Buglet) job numbers do not get re-used (sometimes) Greg Wooledge
  • Re: (Buglet) job numbers do not get re-used (sometimes) Andreas Schwab
  • Re: (Buglet) job numbers do not get re-used (sometimes) Greg Wooledge
  • Re: (Buglet) job numbers do not get re-used (sometimes) Andreas Schwab
  • Re: (Buglet) job numbers do not get re-used (sometimes) Robert Elz
  • Re: (Buglet) job numbers do not get re-used (sometimes) Chet Ramey
  • Re: (Buglet) job numbers do not get re-used (sometimes) Stan Marsh
  • Re: (Buglet) job numbers do not get re-used (sometimes) Stan Marsh
  • Re: (Buglet) job numbers do not get re-used (sometimes) Stan Marsh
  • Re: (Buglet) job numbers do not get re-used (sometimes) Chet Ramey
• localename.h:92:3: error: expected declaration specifiers before '_GL_ATTRIBUTE_CONST' Tianon Gravi
  • Re: localename.h:92:3: error: expected declaration specifiers before '_GL_ATTRIBUTE_CONST' Duncan Roe
  • Re: localename.h:92:3: error: expected declaration specifiers before '_GL_ATTRIBUTE_CONST' Chet Ramey
• Basht: a fork of bash-5.3 adapted to a line-multiplexed tagged display Scott Franco
• readline 8.3: cursor misplaced inside prompt after terminal widening, when the prompt has 2+ invisible-character runs Lucas Grigolon Varela
  • Re: readline 8.3: cursor misplaced inside prompt after terminal widening, when the prompt has 2+ invisible-character runs Chet Ramey
  • Re: readline 8.3: cursor misplaced inside prompt after terminal widening, when the prompt has 2+ invisible-character runs Lucas Grigolon Varela
• [bug #68602] prompt text corrupts when switching modes in vi-mode tmp0x
• prompt text corrupts when switching modes in vi-mode &&&&&&&&&&
• [bash] Variable-name parsing consumes first byte of following multibyte UTF-8 character zheng
  • Re: [bash] Variable-name parsing consumes first byte of following multibyte UTF-8 character Chet Ramey
  • Re: [bash] Variable-name parsing consumes first byte of following multibyte UTF-8 character Grisha Levit
• Re: [PATCH] multibyte_identifiers: opt-in ... Stan Marsh
  • Re: [PATCH] multibyte_identifiers: opt-in ... Chet Ramey
  • Re: [PATCH] multibyte_identifiers: opt-in ... Stan Marsh
• Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch (Ruben.Vanlus) Wiley Young
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch (Ruben.Vanlus) [email protected]
• (Trivial) Wording in 'help variable' refers to Unix Stan Marsh
  • Re: (Trivial) Wording in 'help variable' refers to Unix Chet Ramey
• Re: interactive documentation for read builtin differes from manual, leaves out critical info Britton Kerin
  • Re: interactive documentation for read builtin differes from manual, leaves out critical info Chet Ramey
• Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names... Stan Marsh
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names... Stan Marsh
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names... Wiley Young
  • AW: Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names... Ruben.Vanlus
• Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Robert Elz
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Andreas Schwab
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Robert Elz
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Eduardo Bustamante
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Robert Elz
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Ruben.Vanlus
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Léa Gris
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Ruben.Vanlus
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Chet Ramey
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch jan . smith--- via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Sebastian Peters via Bug reports for the GNU Bourne Again SHell
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Léa Gris
  • Re: [PATCH] multibyte_identifiers: opt-in UTF-8 variable names (UAX #31 + NFC) behind a root-controlled system switch Sebastian Peters via Bug reports for the GNU Bourne Again SHell
• interactive documentation for read builtin differes from manual, leaves out critical info Britton Kerin
  • Re: interactive documentation for read builtin differes from manual, leaves out critical info Chet Ramey
• Re: bug-bash Digest, Vol 284, Issue 16 Wiley Young
• [bug #68534] heap-buffer-overflow in ansicstr/bexpand: size_t to int truncation allocates 12-byte buffer for ~2 GB write Denis Rastyogin
• Possible to add non-existing directory with pushd -n Marcus Johansson via Bug reports for the GNU Bourne Again SHell
  • Re: Possible to add non-existing directory with pushd -n Chet Ramey
  • Re: Possible to add non-existing directory with pushd -n Wiley Young
• [PATCH 0/4] Fix build failures when multibyte support is disabled Shubham Chakraborty
  • [PATCH 1/4] builtins/printf.def: fix build when HANDLE_MULTIBYTE is undefined Shubham Chakraborty
  • [PATCH 3/4] builtins/printf.def: fix type mismatch in tescape call Shubham Chakraborty
  • [PATCH 4/4] lib/glob/smatch.c: fix build failure when multibyte support is disabled Shubham Chakraborty
  • [PATCH 2/4] lib/glob/glob.c: fix build failure when multibyte support is disabled Shubham Chakraborty
  • Re: [PATCH 0/4] Fix build failures when multibyte support is disabled Chet Ramey
  • [PATCH v2 0/4] Fix build failures when multibyte support is disabled Shubham Chakraborty
  • [PATCH v2 2/4] lib/glob/glob.c: fix build failure when multibyte support is disabled Shubham Chakraborty
  • [PATCH v2 1/4] builtins/printf.def: fix build when HANDLE_MULTIBYTE is undefined Shubham Chakraborty
  • [PATCH v2 4/4] include/shmbutil.h: fix build failure when multibyte support is disabled Shubham Chakraborty
  • [PATCH v2 3/4] builtins/printf.def: fix type mismatch in tescape call Shubham Chakraborty
• Re: Wiley Young
• bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Julián Mateu
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Greg Wooledge
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Chet Ramey
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Chet Ramey
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Julián Mateu
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Chet Ramey
  • Re: bash 5.3: here-document larger than PIPE_BUF deadlocks on macOS (pipe-backed heredoc, body written before reader is forked) Julián Mateu
• bash reference munual 5.3 mistype in_many
  • Re: bash reference munual 5.3 mistype Chet Ramey
  • bash reference munual 5.3 mistype in_many
  • Re: bash reference munual 5.3 mistype Chet Ramey
• Bug report: Ambiguous wording in the Signals section of the Bash manual Anton
  • Re: Bug report: Ambiguous wording in the Signals section of the Bash manual Robert Elz
  • Re: Bug report: Ambiguous wording in the Signals section of the Bash manual Chet Ramey
• Re: ECCN "SHELL AND BASH SCRIPTING LANGUAGES" Request Stan Marsh

• Earlier messages