bug-bash
[Top][All Lists]
Advanced

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

Re: nofork command substitution


From: Dale R. Worley
Subject: Re: nofork command substitution
Date: Thu, 18 May 2023 21:58:58 -0400

Á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:

>     There is an alternate form of command substitution:
> 
>       ${C COMMAND; }
> 
> where the character C following the open brace is a space, tab, newline,
> '(', or '|'.  This form executes COMMAND in the current execution
> environment.  This means that side effects of COMMAND take effect
> immediately in the current execution environment and persist in the
> current environment after the command completes (e.g., the 'exit'
> builtin will exit the shell).
> 
> The close brace must be in a position where a
> reserved word may appear (i.e., preceded by a command terminator such as
> semicolon).  ...

Dale



reply via email to

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