Re: Incorrect alias expansion within command substitution

[Alex fxmbsw7 Ratchev]

On Fri, Feb 4, 2022 at 8:28 PM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 2/4/22 2:23 PM, Alex fxmbsw7 Ratchev wrote:
>
> >      > imho the example above should have resulted in error ')'
> >      > it would execute cat a b ) with hello till $( then rather \n and a b 
> > )
> >      > again, useless
> >      > especially the $( wasnt even quoted
> >
> >     What can this possibly mean? What semantic interpretation would lead you
> >     to the conclusion that you should stop reading the token after a `$(' in
> >     this one specific case?
> >
> >
> > by flat non lexical text parsing, excepts for quotes but then $( logically
> > expands, excepts:
> > but imho the topic here is how far to expand shell stuff at this position,
> > however factically its just needs to be a constant data separator
>
> Well, you'd certainly have something here if your shell did that. It
> wouldn't be a POSIX shell, though.

it was my mind shell

does it mean it wont ever get to be the regex /<<([^ \t\f\v\r\n;]+)

that is, after << is parsed a read word till next space, no shell expansion
logic of separated functional structures in the topic of flat data is
overruling, you are overseeing

for me <<$( e o f )
blabla
$( e o f )

is pure early bug

>
> --
> ``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/