Re: [1003.1(2013)/Issue7+TC1 0000953]: Alias expansion is under-specified

2019-02-01 Thread Robert Elz
Date:Fri, 1 Feb 2019 20:46:18 + From:Harald van Dijk Message-ID: | Your proposed wording makes this conditional on whether or not | the token is the first in the input stream. That wasn't the intent - there was an alternation, either the first token (which

Re: [1003.1(2013)/Issue7+TC1 0000953]: Alias expansion is under-specified

2019-02-01 Thread Harald van Dijk
On 01/02/2019 09:56, Robert Elz wrote: Date:Fri, 1 Feb 2019 08:00:16 + From:Harald van Dijk Message-ID: <5cd22a9c-b213-8ffb-da45-f71057eba...@gigawatt.nl> | I was referring to the second token on the second line, which is foo, | not foo=bar. Oh,

Re: [1003.1(2013)/Issue7+TC1 0000953]: Alias expansion is under-specified

2019-02-01 Thread Harald van Dijk
On 01/02/2019 09:53, Geoff Clare wrote: I agree that's an improvement, but I see one slight problem with it: it says "tokens previously read from the input" but the previous tokens could have come from an alias substitution. Here's an attempt to fix that: * the TOKEN could be parsed as

Re: [1003.1(2013)/Issue7+TC1 0000953]: Alias expansion is under-specified

2019-02-01 Thread Harald van Dijk
On 01/02/2019 02:55, Robert Elz wrote: Date:Thu, 31 Jan 2019 22:04:30 + From:Harald van Dijk Message-ID: <126fa44f-05bb-abc2-d6c9-40b82b36f...@gigawatt.nl> |alias foo=bar |echo foo | | alias substitution should not be performed on "foo".