On 8/30/26 9:16 PM, Robert Elz wrote:

[In bash, one can use just '!' as the command:
        empty() { !; }
anywhere a command is required, but that is, like our '{ }', non-standard.
It probably isn't documented though, I didn't check, so don't assume it
won't get fixed sometime.]

The bash parser allows a null command after `time', and it was a chore to
do it, but ksh93 allowed it and it looked for a while like POSIX was going
to require it (https://www.austingroupbugs.net/view.php?id=267, a
"Shelltime pipeline"). That didn't end up happening.

The empty command after `!' was also specified in the same interpretation
(a `False pipeline').

POSIX approved the interp in 2010, changed its mind in 2020 based on a
report from 2016, then made the whole business unspecified in 2022. Of
course, by that time, it had been in bash for years.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    [email protected]    http://tiswww.cwru.edu/~chet/

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to