bug-bash
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [PATCH] printf: add %#s alias to %b
Oğuz
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Oğuz
Re: [PATCH] printf: add %#s alias to %b
Chet Ramey
Re: [PATCH] printf: add %#s alias to %b
William Bader
Re: [PATCH] printf: add %#s alias to %b
Chet Ramey
Re: [PATCH] printf: add %#s alias to %b
Eric Blake
Re: [PATCH] printf: add %#s alias to %b
Chet Ramey
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Zachary Santer
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Eric Blake
Re: [PATCH] printf: add %#s alias to %b
Pádraig Brady
Re: [PATCH] printf: add %#s alias to %b
Zachary Santer
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Greg Wooledge
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Dragan Simic
Re: [PATCH] printf: add %#s alias to %b
Chet Ramey
Re: [PATCH] printf: add %#s alias to %b
Dragan Simic
Re: [PATCH] printf: add %#s alias to %b
Rob Landley
Re: [PATCH] printf: add %#s alias to %b
Dragan Simic
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Dragan Simic
Re: [PATCH] printf: add %#s alias to %b
Eric Blake
Re: [PATCH] printf: add %#s alias to %b
Robert Elz
Re: [PATCH] printf: add %#s alias to %b
Eric Blake
Re: [PATCH] printf: add %#s alias to %b
Rob Landley
RFC: changing printf(1) behavior on %b
Eric Blake
Re: RFC: changing printf(1) behavior on %b
Chet Ramey
Re: bug#65659: RFC: changing printf(1) behavior on %b
Eric Blake
Re: bug#65659: RFC: changing printf(1) behavior on %b
Emanuele Torre
Re: bug#65659: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: bug#65659: RFC: changing printf(1) behavior on %b
Eric Blake
Re: bug#65659: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: RFC: changing printf(1) behavior on %b
Phi Debian
Re: RFC: changing printf(1) behavior on %b
Phi Debian
Re: bug#65659: RFC: changing printf(1) behavior on %b
Eric Blake
Re: bug#65659: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: bug#65659: RFC: changing printf(1) behavior on %b
Steffen Nurpmeso
Re: bug#65659: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: bug#65659: RFC: changing printf(1) behavior on %b
Steffen Nurpmeso
Re: bug#65659: RFC: changing printf(1) behavior on %b
Phi Debian
Re: bug#65659: RFC: changing printf(1) behavior on %b
Léa Gris
Re: RFC: changing printf(1) behavior on %b
Oğuz
Re: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: bug#65659: RFC: changing printf(1) behavior on %b
Paul Eggert
Re: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: RFC: changing printf(1) behavior on %b
Stephane Chazelas
Re: RFC: changing printf(1) behavior on %b
Martin D Kealey
Some incorrect behaviour for BASH arrays
Victor Pasko
Re: Some incorrect behaviour for BASH arrays
Lawrence Velázquez
Re: Some incorrect behaviour for BASH arrays
Victor Pasko
Re: Some incorrect behaviour for BASH arrays
Kerin Millar
Re: Some incorrect behaviour for BASH arrays
Kerin Millar
Re: Some incorrect behaviour for BASH arrays
Greg Wooledge
Fwd: Some incorrect behaviour for BASH arrays
Victor Pasko
Re: Fwd: Some incorrect behaviour for BASH arrays
Kerin Millar
Re: Fwd: Some incorrect behaviour for BASH arrays
Victor Pasko
bug attached
queency3 jones
Re: bug attached
Chet Ramey
Re: bug attached
Andreas Kusalananda Kähäri
Re: bug attached
queency3 jones
Re: bug attached
Chet Ramey
Re: bug attached
Greg Wooledge
Re: bug attached
Andreas Kusalananda Kähäri
Re: bug attached
queency3 jones
test -v difference between bash 5.1 and 5.2
Christian Schneider
Re: test -v difference between bash 5.1 and 5.2
Chet Ramey
Re: test -v difference between bash 5.1 and 5.2
Kerin Millar
Re: test -v difference between bash 5.1 and 5.2
Chet Ramey
Re: test -v difference between bash 5.1 and 5.2
Kerin Millar
Re: test -v difference between bash 5.1 and 5.2
Chet Ramey
Re: test -v difference between bash 5.1 and 5.2
Christian Schneider
Re: test -v difference between bash 5.1 and 5.2
Kerin Millar
Re: test -v difference between bash 5.1 and 5.2
Chet Ramey
Re: test -v difference between bash 5.1 and 5.2
Kerin Millar
[PATCH] consistent BASH_COMMAND, DEBUG trap, xtrace order
Grisha Levit
Re: [PATCH] consistent BASH_COMMAND, DEBUG trap, xtrace order
Chet Ramey
give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Chet Ramey
Re: give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Martin D Kealey
Re: give_terminal_to() / maybe_give_terminal_to() race
Chet Ramey
Re: give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Chet Ramey
Re: give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Chet Ramey
Re: give_terminal_to() / maybe_give_terminal_to() race
Earl Chew
Re: give_terminal_to() / maybe_give_terminal_to() race
Chet Ramey
[PATCH] Remove maybe_give_terminal_to() race
Earl Chew
[PATCH] Use SIGCONT to avoid fg tcsetpgrp() SIGTTIN/SIGTTOU race
Earl Chew
Re: [PATCH] Use SIGCONT to avoid fg tcsetpgrp() SIGTTIN/SIGTTOU race
Chet Ramey
Re: [PATCH] Use SIGCONT to avoid fg tcsetpgrp() SIGTTIN/SIGTTOU race
Earl Chew
[PATCH] leak in cut example loadable builtin
Grisha Levit
heap-buffer-overflow in finfo.c
Grisha Levit
Re: heap-buffer-overflow in finfo.c
Chet Ramey
Error handling with nofork command substitution
jm
read -E with read -d in completion function
Grisha Levit
Re: read -E with read -d in completion function
Chet Ramey
Re: remove empty '' in ${var@Q} result?
Clark Wang
Re: remove empty '' in ${var@Q} result?
Chet Ramey
using exec to close a fd in a var crashes bash
jleivent
Re: using exec to close a fd in a var crashes bash
Greg Wooledge
Re: using exec to close a fd in a var crashes bash
Grisha Levit
Re: using exec to close a fd in a var crashes bash
Chet Ramey
Re: using exec to close a fd in a var crashes bash
Martin D Kealey
Re: using exec to close a fd in a var crashes bash
Chet Ramey
Re: using exec to close a fd in a var crashes bash
Dale R. Worley
Re: using exec to close a fd in a var crashes bash
Chet Ramey
Re: using exec to close a fd in a var crashes bash
Greg Wooledge
Re: using exec to close a fd in a var crashes bash
Martin D Kealey
Re: using exec to close a fd in a var crashes bash
Greg Wooledge
Re: using exec to close a fd in a var crashes bash
Martin D Kealey
Re: using exec to close a fd in a var crashes bash
Zachary Santer
Re: using exec to close a fd in a var crashes bash
Greg Wooledge
Re: using exec to close a fd in a var crashes bash
Andreas Schwab
Re: using exec to close a fd in a var crashes bash
Ángel
Re: using exec to close a fd in a var crashes bash
Chet Ramey
Re: using exec to close a fd in a var crashes bash
alex xmb ratchev
nofork comsub in PS1 + ignoreeof
Grisha Levit
Re: nofork comsub in PS1 + ignoreeof
Chet Ramey
SLA Information
Malena Arduino via Bug reports for the GNU Bourne Again SHell
Re: SLA Information
Martin D Kealey
Re: SLA Information
Chet Ramey
pathological bash-malloc behaviour
Sergei Trofimovich
[REGRESSION] Incorrect libcurses detection in 5.2.15 (on HP-UX)
Osipov, Michael (IN IT IN)
Assignment to RO variable
Wiley Young
Re: Assignment to RO variable
Dennis Williamson
formatting man pages in email (was: Assignment to RO variable)
G. Branden Robinson
Re: formatting man pages in email (was: Assignment to RO variable)
Phi Debian
Re: Assignment to RO variable
Greg Wooledge
Re: Assignment to RO variable
Martin D Kealey
Re: Assignment to RO variable
Chet Ramey
String replacement drops leading '-e' if replacing char is a space
pphick via Bug reports for the GNU Bourne Again SHell
Re: String replacement drops leading '-e' if replacing char is a space
Eduardo Bustamante
Re: String replacement drops leading '-e' if replacing char is a space
Lawrence Velázquez
Re: String replacement drops leading '-e' if replacing char is a space
Zachary Santer
Re: String replacement drops leading '-e' if replacing char is a space
Kerin Millar
Re: String replacement drops leading '-e' if replacing char is a space
Greg Wooledge
!& error
Grisha Levit
Re: !& error
Chet Ramey
Re: !& error
Grisha Levit
Re: !& error
Chet Ramey
errexit is not respected on nested functions when parent function preceeds ||
cirrus . mazurka-0t--- via Bug reports for the GNU Bourne Again SHell
Re: errexit is not respected on nested functions when parent function preceeds ||
Lawrence Velázquez
!; is interpreted as an history expansion that can never match anything
Emanuele Torre
! history expansion occurs within arithmetic substitutions
Zachary Santer
Re: ! history expansion occurs within arithmetic substitutions
Emanuele Torre
Re: ! history expansion occurs within arithmetic substitutions
Martin D Kealey
Re: ! history expansion occurs within arithmetic substitutions
Dale R. Worley
Re: ! history expansion occurs within arithmetic substitutions
Andreas Schwab
Re: ! history expansion occurs within arithmetic substitutions
Dale R. Worley
Re: ! history expansion occurs within arithmetic substitutions
Martin D Kealey
Re: ! history expansion occurs within arithmetic substitutions
Chet Ramey
Re: ! history expansion occurs within arithmetic substitutions
Martin D Kealey
Re: ! history expansion occurs within arithmetic substitutions
Zachary Santer
Re: ! history expansion occurs within arithmetic substitutions
Dale R. Worley
Re: ! history expansion occurs within arithmetic substitutions
Lawrence Velázquez
Re: !; is interpreted as an history expansion that can never match anything
Dale R. Worley
Re: !; is interpreted as an history expansion that can never match anything
Chet Ramey
Re: !; is interpreted as an history expansion that can never match anything
Chet Ramey
Re: !; is interpreted as an history expansion that can never match anything
Emanuele Torre
Re: !; is interpreted as an history expansion that can never match anything
Chet Ramey
BASH_SUBSHELL is not incrementing when part of a pipeline
Kamil Cukrowski Priv
Re: BASH_SUBSHELL is not incrementing when part of a pipeline
Greg Wooledge
Re: BASH_SUBSHELL is not incrementing when part of a pipeline
Chet Ramey
assoc vs array append
Grisha Levit
Re: assoc vs array append
Chet Ramey
[PATCH] declare -g compound assignment with associative array
Grisha Levit
Re: [PATCH] declare -g compound assignment with associative array
Chet Ramey
[PATCH] getconf CHAR_BIT -> CHAR_MAX
Grisha Levit
[PATCH] fix getconf pathconf arg validation
Grisha Levit
[PATCH] fix getconf builtin ifdef's
Grisha Levit
A few suggestions for the GNU Manual
Wiley Young
Re: A few suggestions for the GNU Manual
Chet Ramey
[PATCH] use real compspec hash key for compopt output
Grisha Levit
Re: [PATCH] use real compspec hash key for compopt output
Chet Ramey
history builtin with no HISTFILE
Grisha Levit
Re: history builtin with no HISTFILE
Chet Ramey
Re: history builtin with no HISTFILE
Grisha Levit
Re: history builtin with no HISTFILE
Chet Ramey
comments inside command subst are handled inconsistently
Denys Vlasenko
Re: comments inside command subst are handled inconsistently
Dale R. Worley
Re: comments inside command subst are handled inconsistently
Martin D Kealey
Re: comments inside command subst are handled inconsistently
Chet Ramey
Re: comments inside command subst are handled inconsistently
Martin D Kealey
Re: comments inside command subst are handled inconsistently
Chet Ramey
Re: comments inside command subst are handled inconsistently
Ángel
Re: comments inside command subst are handled inconsistently
Denys Vlasenko
Re: comments inside command subst are handled inconsistently
G. Branden Robinson
Re: comments inside command subst are handled inconsistently
Chet Ramey
Re: comments inside command subst are handled inconsistently
Chet Ramey
Re: comments inside command subst are handled inconsistently
Denys Vlasenko
Re: comments inside command subst are handled inconsistently
G. Branden Robinson
Re: comments inside command subst are handled inconsistently
Chet Ramey
built-in printf returns success when integer is out of range
thomas
Re: built-in printf returns success when integer is out of range
Dennis Williamson
Re: built-in printf returns success when integer is out of range
thomas
Earlier messages
Later messages