On 3/21/24 12:13 PM, Gioele Barabucci wrote:
If this behavior is desired and not considered a bug, then the bash manual should describe it in the SIGNALS section.When bash runs a builtin command without forking, it should install a SIGPIPE handler that will cause that signal to abort the command but not terminate the shell.
It's described in the COMMAND EXECUTION section. The execution environment
for shell builtins and functions is the same as the shell environment: it
has none of the changes described in the "simple command other than a
builtin or shell function" execution environment. In particular, the signal
handlers and trapped signals are identical to the calling shell.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
OpenPGP_signature.asc
Description: OpenPGP digital signature
