[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nofork command substitution
From: |
alex xmb ratchev |
Subject: |
Re: nofork command substitution |
Date: |
Fri, 19 May 2023 14:25:15 +0200 |
On Fri, May 19, 2023, 13:54 Greg Wooledge <greg@wooledge.org> wrote:
> On Fri, May 19, 2023 at 01:36:44PM +0200, alex xmb ratchev wrote:
> > 'C ..'
> > ' ..'
> > '| ..'
> >
> > .. i dont get it
>
> Yeah, the wording isn't ideal. I'd start it out like this:
>
yea better ..
${ COMMAND; }
> ${| COMMAND; }
>
what about ${C COMMAND}
Execute COMMAND in the current execution environment....
>
> The first form (where the character after ${ is a space, tab or newline)
> does such and such....
>
> The second form (where the character after ${ is a pipe) does so and so....
thxx
>
- Re: nofork command substitution, (continued)
- Re: nofork command substitution, Robert Elz, 2023/05/19
- Re: nofork command substitution, alex xmb ratchev, 2023/05/19
- Re: nofork command substitution, alex xmb ratchev, 2023/05/19
- Re: nofork command substitution, Chet Ramey, 2023/05/22
- Re: nofork command substitution, Martijn Dekker, 2023/05/22
Re: nofork command substitution, Chet Ramey, 2023/05/19
Re: nofork command substitution, alex xmb ratchev, 2023/05/19
Re: nofork command substitution, Chet Ramey, 2023/05/19
Re: nofork command substitution, Grisha Levit, 2023/05/19
Re: nofork command substitution, Koichi Murase, 2023/05/23