bash does not run exit traps if the last command is a kill builtin that kills bash (`kill "$$"')

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash

Re: bug#54785: for floating point, printf should use double like in C instead of long double

On 4/25/22 3:06 PM, Paul Eggert wrote: On 4/25/22 11:22, Chet Ramey wrote: Thanks for the input. You're welcome. Whenever you decide what to do about this, could you please let us know? I'd like coreutils printf to stay compatible with Bash printf. Thanks. I think I'm going to stick with t

Bug in documentation (man)

Hi Gnu, I bash 5.1 man it says that pipeline may consist of single command. So "echo foo" is a pipeline. It also says that each command in pipeline runs in a subshell, therefore "echo foo" runs in a subshell. But thats not true. Regards Gasan

Re: bug#54785: for floating point, printf should use double like in C instead of long double

On 4/29/22 13:04, Chet Ramey wrote: I think I'm going to stick with the behavior I proposed, fixing the POSIX conformance issue and preserving backwards compatibility, until I hear more about whether backwards compatibility is an issue here. Come to think of it, as far as POSIX is concerned Ba