bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nofork command substitution


From: Chet Ramey
Subject: Re: nofork command substitution
Date: Fri, 19 May 2023 10:18:47 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0

On 5/18/23 9:58 PM, Dale R. Worley wrote:
Ángel <angel@16bits.net> writes:
I suggest:

     There is an alternate form of command substitution:
${ COMMAND; }

and clarify later the other variants in addition to a space:

The character following the open brace must be a space, tab,
newline, '(', or '|', and the close brace must be in a position...

I support either that change, or reordering the text to specify "C" at
the beginning, when the syntax is being described, before the semantics
are described:

I think it's more important to describe the primary reason it differs from
standard command substitution before getting into the syntax.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]