On 09/01/2019 12:29, Austin Group Bug Tracker wrote:
[...] > --
(0004201) geoffclare (manager) - 2019-01-09 12:29
http://austingroupbugs.net/view.php?id=953#c4201
Date:Wed, 9 Jan 2019 17:35:10 +
From:Stephane Chazelas
Message-ID: <20190109173510.xn4hdeqphbffb...@chaz.gmail.com>
| I'd rather POSIX forbade applications to use "while", "until",
| "do", "select", "time", etc in alias names, or leave it
| unspecified
2019-01-09 18:24:47 +0100, Joerg Schilling:
[...]
> They also had the idea of implementing a shell builtin that behaves like:
>
> sh -c cmd args
>
> and thus could support parameterized macros.
[...]
That can only really be used for "parameterized macros" that
could be done as
One concern I have is that if I understand correctly, it
*allows* application to do:
alias 'while=until'
(though doesn't for other keywords like "{", "!")
and then *requires* implementations to expand "while" in
alias 'echo_expand=echo '
echo_expand while
and *requires* implementations *not*
Robert Elz wrote:
> | Then in 1980, former AT people that created the company "Charles River
> Data
> | Systems" and the first UNIX clone "UNOS" created an alias implementation
> | concept that sits in the lexer and expands text. This is the most powerful
> | alias concept that has
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1224
==
Reported By:geoffclare
Assigned To:
On 1/7/19 6:55 AM, Joerg Schilling wrote:
> The way I have the teleconference in mind where we set up the new text, the
> above commands causes undefined results because the shell is _allowed_ but
> not
> required to parse scripts as a whole under some conditions.
I think Geoff's proposed
Robert Elz wrote, on 09 Jan 2019:
>
> There are just a couple of minor points that I have with your
> wording, one where I think a little more clarity is needed, and
> one where your wording isn't quite correct.
>
>
> | ... change to:
>
> | After a TOKEN has been delimited,
>
> This is
Date:Wed, 9 Jan 2019 13:27:58 +
From:"Schwarz, Konrad"
Message-ID:
| I think it would reduce confusion if it were explicitly mandated.
That is not what this group does, and not what any standards
group should do - the objective is to work out what is the
Date:Wed, 9 Jan 2019 12:29:45 +
From:Austin Group Bug Tracker
Message-ID: <95df9c99cbc201dbbf9de3d53079d...@austingroupbugs.net>
| please reply on the
| mailing list and (if I agree) I will edit this note.
I wish the part of all of this that really belongs
On 1/9/19 8:27 AM, Schwarz, Konrad wrote:
>> -Original Message-
>> Expressly making it defined that
>> alias foo='whatever \ '
>> which does end in a space (but otherwise is the exact same thing as the
>> previous one) also does not expand aliases in the following
>> word
>> seems
Date:Wed, 9 Jan 2019 13:55:16 +0100
From:Joerg Schilling
Message-ID: <5c35ef34.clu1godeocvhzivr%joerg.schill...@fokus.fraunhofer.de>
| Well, the original Bourne Shell did not have aliases.
Yes, I know that...
| I believe that csh introduced an alias concept in
> -Original Message-
> Expressly making it defined that
> alias foo='whatever \ '
> which does end in a space (but otherwise is the exact same thing as the
> previous one) also does not expand aliases in the following
> word
> seems redundant to me. Since several shells (but not
Robert Elz wrote:
> Date:Tue, 8 Jan 2019 23:01:05 +
> From:Stephane Chazelas
> Message-ID: <20190108230105.43xiupnfx4qwy...@chaz.gmail.com>
>
> | aliases come from csh which did not do that expansion after
> | trailing blank thing.
>
> Actually from ashell,
Robert Elz wrote:
> Date:Tue, 8 Jan 2019 16:51:04 +
> From:Geoff Clare
> Message-ID: <20190108165104.GA31969@lt2.masqnet>
>
>
> | Given Chet's reply, it looks like there may be more shells that do expand
> | than don't. In which case I wonder why that
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=953
==
Reported By:wpollock
Assigned To:
Date:Wed, 9 Jan 2019 10:44:00 + (UTC)
From:Shware Systems
Message-ID: <886936614.8618146.1547030640...@mail.yahoo.com>
| Alias bodies may include entire or partial compound statements, expansions,
| redirections, and unclosed strings of the <">, <'>, or <$'>
Date:Wed, 9 Jan 2019 10:05:21 +
From:Geoff Clare
Message-ID: <20190109100521.GC690@lt2.masqnet>
| It's not obvious to me. Alias lookup has already been done for the
| word in that position in the input and there is nothing to suggest
| the shell has to go
Robert Elz wrote, on 09 Jan 2019:
>
> | This surprised me. I was previously unaware that the first word in
> | the alias value is subject to recursive alias expansion. There is
> | nothing in the standard to suggest this happens!
>
> There certainly isn't in the current (published) text,
Chet Ramey wrote, on 08 Jan 2019:
>
> On 1/8/19 11:51 AM, Geoff Clare wrote:
> > Robert Elz wrote, on 08 Jan 2019:
> >>
> >> | I would prefer that we not leave it unspecified when an alias ends
> >> with "\ ".
> >> | If there is a shell which does recursive alias expansion in this case,
>
Shware Systems wrote, on 09 Jan 2019:
>
> On Tuesday, January 8, 2019 Robert Elz wrote:
>
>> ps: (and this bit might be relevant to the discussions) - it js really
>> hard to imagine a use for an alias with a definition that ends "\ "
>> (the only way to get a quoted space as the final char in
21 matches
Mail list logo
