[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Incorrect alias expansion within command substitution
From: |
Alex fxmbsw7 Ratchev |
Subject: |
Re: Incorrect alias expansion within command substitution |
Date: |
Sat, 5 Feb 2022 00:21:09 +0100 |
it seems me here the data was used as var inside $(( not as alias
i tried d1 d2 d3 combination and didnt work
On Sat, Feb 5, 2022 at 12:17 AM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> wrote:
>
> what about this viewing point
> aliases can start, $(('s, but not end... this is unlogic
>
> alias -- \
> p='printf %s\\n ' \
> assign='assign=$(( ' begin='$(( ' \
>
> for data in "1 + 2"
> do
> alias -- data="$d "
> p begin data ))
> done
>
> this works and results 3
>
> its just, early bugs, unlogic :)
>
> On Sat, Feb 5, 2022 at 12:11 AM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
> wrote:
> >
> >
> >
> > 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/
- Re: Incorrect alias expansion within command substitution, (continued)
- Re: Incorrect alias expansion within command substitution, Robert Elz, 2022/02/04
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/04
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/04
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/04
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/04
- Re: Incorrect alias expansion within command substitution,
Alex fxmbsw7 Ratchev <=
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Lawrence Velázquez, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Chet Ramey, 2022/02/05
- Re: Incorrect alias expansion within command substitution, Alex fxmbsw7 Ratchev, 2022/02/05