Martijn Dekker wrote, on 10 Apr 2018:
>
> Re: https://github.com/att/ast/issues/71
>
> Consider this test script:
>
> (set -o posix) 2>/dev/null && set -o posix
> emulate sh 2>/dev/null # for zsh
> for var in 'a-c' '!a'; do
> case b in
> ( ["$var"] )echo
I wrote:
>
> And I believe the standard does clearly require the ksh88/bash
> behaviour because of this statement in 2.2.3 Double-Quotes:
>
> Enclosing characters in double-quotes ("") shall preserve the
> literal value of all characters within the double-quotes, with the
> exception
Geoff Clare wrote:
> Robert Elz wrote, on 11 Apr 2018:
> >
> > Lower down, it says ...
> >
> > In order from the beginning to the end of the case statement, each
> > pattern
> > that labels a compound-list shall be subjected to tilde expansion,
Date:Wed, 11 Apr 2018 10:00:27 +0100
From:Geoff Clare
Message-ID: <20180411090027.GA18582@lt2.masqnet>
| There is nothing to suggest that this does not apply to the characters
| which, when unquoted, have a special meaning within bracket
Martijn Dekker wrote:
> Op 10-04-18 om 21:06 schreef Robert Elz:
> > Date:Tue, 10 Apr 2018 13:41:25 +0100
> > From:Martijn Dekker
> > Message-ID:
> >
> >| Does POSIX specify
Date:Wed, 11 Apr 2018 11:28:38 +0200
From:Joerg Schilling
Message-ID: <5acdd546.fkln7tigk21a+de6%joerg.schill...@fokus.fraunhofer.de>
| The problem is that the term "quote removal" is not related to a real
verified
| shell
Martijn Dekker wrote:
> Op 10-04-18 om 15:59 schreef Joerg Schilling:
> > Whom do you call "current ksh93 lead developers"?
>
> As far as I can tell from what's going on at the github repo, Siteshwar
> Vashisht and Kurtis Rader currently appear to be in charge of its
>
Robert Elz wrote, on 11 Apr 2018:
>
> Lower down, it says ...
>
> In order from the beginning to the end of the case statement, each
> pattern
> that labels a compound-list shall be subjected to tilde expansion,
> parameter
> expansion, command
Geoff Clare wrote:
> Here's a much simpler demonstration of the same "quoting within
> brackets" issue:
>
> $ ls
> b
>
> ksh93:
> $ echo ["a-c"]
> b
>
> ksh88 and bash:
> $ echo ["a-c"]
> [a-c]
>
> As Joerg pointed out, the intention would have been for POSIX to
> specify the
Robert Elz wrote, on 11 Apr 2018:
>
> Incidentally, I know that this part of the 985 new text ...
>
> the first argument (pattern) is the same as patt, except each character
> that was quoted in patt and is not in a bracket expression is prefixed
> by a backslash
Date:Wed, 11 Apr 2018 12:18:27 +0100
From:Geoff Clare
Message-ID: <2018041827.GA29286@lt2.masqnet>
| No, that text is very careful to say "*was* quoted", not "is quoted",
| for precisely this reason. To conform to this requirement, the
Robert Elz wrote:
> Date:Wed, 11 Apr 2018 11:28:38 +0200
> From:Joerg Schilling
> Message-ID:
> <5acdd546.fkln7tigk21a+de6%joerg.schill...@fokus.fraunhofer.de>
>
> | The problem is that the term "quote
Date:Wed, 11 Apr 2018 14:14:18 +0200
From:Joerg Schilling
Message-ID: <5acdfc1a.st0sitei1fsdsgeb%joerg.schill...@fokus.fraunhofer.de>
| Then we should change the wording.
I agree.
| The characters '.', '*' and '[' really
The following issue is UNDER REVIEW.
==
http://austingroupbugs.net/view.php?id=985
==
Reported By:rhansen
Assigned To:
14 matches
Mail list logo