On Wed, May 03, 2023 at 04:56:16PM -0700, Tianon Gravi wrote:
> I'm getting the following error when building the latest "devel"
> (23935dbe8513437e69ca14d6b0890067dddceba3) on Alpine Linux 3.17:
Techincally ssize_t is not part of standard C, and, according to
POSIX, it should be defined in tha
I'm getting the following error when building the latest "devel"
(23935dbe8513437e69ca14d6b0890067dddceba3) on Alpine Linux 3.17:
| gcc -c -I. -I../.. -I../.. -I../../lib -I../../include -I.
-I../../lib/intl -I/tmp/bash/lib/intl -DHAVE_CONFIG_H -DSHELL -DDEBUG
-Wno-parentheses -Wno-format-securi
This was causing crashes when non-interactive shells that read stdin,
either source a file that dups stdin, or run an eval command that dups
stdin:
$ bash <<< 'echo hi 9<&0'
hi
$ printf %s\\n 'echo hi 9<&0' > file; bash <<< '. ./file'
Segmentation fault (core dumped)
$ bash <<< 'eval "ec
On 4/26/23 5:38 PM, Grisha Levit wrote:
A few issues with EOF being received at PS2:
The setting of ignoreeof is ignored at PS2:
bash --norc -o ignoreeof
$ uname \
^D
Linux
(bash exits)
It's never been active in this situation, because it doesn't meet the
criteria for ignoreeof: EOF on an
On Wed, May 3, 2023, 16:25 Chet Ramey wrote:
> On 4/23/23 1:56 PM, Mark Schlegel wrote:
> > Bash has a history function, it would be useful if 'history' would show
> the exit codes (return codes) from all commands:
>
> Thanks for the proposal. There have been various suggestions over the years
>
On 4/23/23 1:56 PM, Mark Schlegel wrote:
Bash has a history function, it would be useful if 'history' would show the
exit codes (return codes) from all commands:
Thanks for the proposal. There have been various suggestions over the years
about additional information attached to each history en
On 4/25/23 2:41 PM, Guldrelokk wrote:
POSIX has the following to say with respect to the 'jobs' utility:
When jobs reports the termination status of a job, the shell shall remove
its process ID from the list of those known in the current shell
execution environment
With Bash, this is not the ca
I guess there is not too much to say about the bash built-ins 'true' and
'false'. Nonetheless, I suggest that the info pages should list these
built-ins individually like other built-ins. Currently, the only hint on
their
existence in the info or man page is in the node (or man page section)
calle
I am writing to follow up on this old bug report about the lack of
documentation for the bash built-ins 'true' and 'false'. I agree with the
previous arguments on why these built-ins should be documented in 'info
bash',
and I would like to add two more reasons:
- The commands 'true' and 'false' th
