[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nofork command substitution
From: |
Greg Wooledge |
Subject: |
Re: nofork command substitution |
Date: |
Fri, 19 May 2023 08:55:06 -0400 |
On Fri, May 19, 2023 at 02:25:15PM +0200, alex xmb ratchev wrote:
> 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}
There is no "C". That's what's so confusing about the original wording.
"C" can be either a space, tab, newline, or pipeline, and this explanation
is very far away from the syntax.
- Re: nofork command substitution, (continued)
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