Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

On 6/24/19 12:31 PM, Stephane Chazelas wrote: > 2019-06-24 11:52:56 -0400, Chet Ramey: > [...] >>> Before going in the details of the language, can we at least >>> agree on what the "intention" should be? >> >> Your intention is obvious. It's in the part I quoted. >> >> Pathname expansion is

Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

On 6/24/19 11:49 AM, Stephane Chazelas wrote: > Just tried with the current head of the devel branch from today > (5.0.7(5)-maint). > > In an empty dir: > > $ mkdir -m a=r readable > $ mkdir -m a=x searchable > > $ bash5 -c 'printf "%s\n" */.' > searchable/. > $ bash5 -c 'printf "%s\n" */\.' >

[1003.1(2016)/Issue7+TC2 0001252]: Extend TZ to allow times outside 00-24 range, permanent DST

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1252 == Reported By:eggert Assigned To:

Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

Harald van Dijk wrote: > That aside, I asked you last time you made this claim about POSIX to > back it up. There is no requirement for standard utilities to be > implemented portably. You responded then: > > > POSIX intends to create portability at source code level. > > > > Code that is not

[1003.1(2016)/Issue7+TC2 0001252]: Extend TZ to allow times outside 00-24 range, permanent DST

The following issue has been set as RELATED TO issue 0001253. == http://austingroupbugs.net/view.php?id=1252 == Reported By:eggert Assigned

[1003.1(2016)/Issue7+TC2 0001253]: clarify that "alternative time" means tm_isdst is positive

The following issue has been set as RELATED TO issue 0001252. == http://austingroupbugs.net/view.php?id=1253 == Reported By:eggert Assigned

[1003.1(2016)/Issue7+TC2 0001252]: Extend TZ to allow times outside 00-24 range, permanent DST

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1252 == Reported By:eggert Assigned To:

[1003.1(2016)/Issue7+TC2 0001251]: ex(1): formatting issues in command arguments

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1251 == Reported By:mohd_akram Assigned To:

Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

Harald van Dijk wrote, on 27 Jun 2019: > > On 27/06/2019 10:04, Geoff Clare wrote: > >Stephane Chazelas wrote, on 26 Jun 2019: > >> > >>Or again, forget all about it and treat the ksh93 behaviour as > >>non-compliant as is already the case. > > > >I'm starting to think that this is what we

Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

2019-06-27 10:48:20 -0400, Chet Ramey: > On 6/27/19 2:15 AM, Stephane Chazelas wrote: > > > I could be convinced that it makes sense for the ksh93 X(...) > > operators to be allowed if there was one non-anecdotal > > implementation of fnmatch() that implemented it, but I don't > > think there it.