Re: Incorrect alias expansion within command substitution

[Alex fxmbsw7 Ratchev]

On Fri, Feb 4, 2022, 23:12 Chet Ramey <chet.ramey@case.edu> wrote:

> On 2/4/22 2:56 PM, Alex fxmbsw7 Ratchev wrote:
>
> >>> 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,
>
> That's just not how it works, and never has. There's no exception for the
> word that is the here-doc delimiter. It's a shell word like any other; the
> difference is in the expansions it undergoes.
>
>
> > 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
>
> It's simply not the `flat data' you think it is or should be.
>
> (And that construct is certainly not something anyone should use, `early
> bug' or not.)
>

i see, :)
thanks and sorry

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