On 03/07/2019 15:27, Geoff Clare wrote:
Harald van Dijk wrote, on 03 Jul 2019:
On 03/07/2019 11:08, Geoff Clare wrote:
Stephane Chazelas wrote, on 03 Jul 2019:
2019-07-03 09:24:10 +0100, Geoff Clare:
[...]
[...] If any character (ordinary, shell
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=1267
==
Reported By:dennisw
Assigned To:
Stephane Chazelas wrote, on 03 Jul 2019:
>
> Before (Bourne/ksh88...) it was:
>
> *, ? and [...] are wildcard operators and quoting can be used to
> remove their special meaning.
>
> Which applies to both shell and fnmatch() (where quoting is done
> with \).
>
> With your proposed change, the
Just being picky, re:
"Arguments to find, pax, fnmatch() and glob() are others."
at the bottom, which to me should be:
"Arguments to exec('find',...), exec('pax',...), fnmatch() and glob() are
others."
as parameters of find and pax in scripts are shell words covered by the
statement preceding
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1267
==
Reported By:dennisw
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1266
==
Reported By:dennisw
Assigned To:
2019-07-03 15:19:18 +0100, Geoff Clare:
[...]
> > Irrelevant, pax, fnmatch() and glob() don't do variable
> > expansion. find -name '$a' is unspecified but in all
> > implementations, that returns the files called $a literally.
>
> The goal is consistency of how backslash behaves in patterns.
> A
Harald van Dijk wrote, on 03 Jul 2019:
>
> On 03/07/2019 11:08, Geoff Clare wrote:
> >Stephane Chazelas wrote, on 03 Jul 2019:
> >>
> >>2019-07-03 09:24:10 +0100, Geoff Clare:
> >>[...]
> >>> [...] If any character (ordinary, shell
> >>>special, or pattern
Stephane Chazelas wrote, on 03 Jul 2019:
>
> 2019-07-03 11:08:57 +0100, Geoff Clare:
> [...]
> > > And again, that's an incompatible change for dash, ksh88, ksh93,
> > > pdksh, mksh, bosh, yash where:
> > >
> > > a='\*'
> > > ls -ld $a
> > >
> > > lists the files that start with \
> >
> >
On 03/07/2019 11:08, Geoff Clare wrote:
Stephane Chazelas wrote, on 03 Jul 2019:
2019-07-03 09:24:10 +0100, Geoff Clare:
[...]
[...] If any character (ordinary, shell
special, or pattern special) is quoted or (where shell quoting is not
in effect)
2019-07-03 11:08:57 +0100, Geoff Clare:
[...]
> > And again, that's an incompatible change for dash, ksh88, ksh93,
> > pdksh, mksh, bosh, yash where:
> >
> > a='\*'
> > ls -ld $a
> >
> > lists the files that start with \
>
> Which is inconsistent with find, pax, fnmatch() and glob().
And
On 03/07/2019 09:24, Geoff Clare wrote:
Harald van Dijk wrote, on 02 Jul 2019:
That's not because the word "unquoted" is used, which only applies to shell
quoting, that's because 2.13.1 contains "All of the requirements and effects
of quoting on ordinary, shell special, and special pattern
Joerg Schilling wrote, on 03 Jul 2019:
>
> Geoff Clare wrote:
>
> > Joerg Schilling wrote, on 03 Jul 2019:
>
> > > Do you like to say that pax behaves inconsistent to ls?
> >
> > The inconsistentcy has nothing to do with ls. It's with how those
> > shells interpret the (indirect) pattern \*
Geoff Clare wrote:
> Joerg Schilling wrote, on 03 Jul 2019:
> > Do you like to say that pax behaves inconsistent to ls?
>
> The inconsistentcy has nothing to do with ls. It's with how those
> shells interpret the (indirect) pattern \* compared to how find, pax,
> fnmatch() and glob() (and the
Joerg Schilling wrote, on 03 Jul 2019:
>
> Geoff Clare wrote:
>
> > Stephane Chazelas wrote, on 03 Jul 2019:
> > > And again, that's an incompatible change for dash, ksh88, ksh93,
> > > pdksh, mksh, bosh, yash where:
> > >
> > > a='\*'
> > > ls -ld $a
> > >
> > > lists the files that start
Geoff Clare wrote:
> Stephane Chazelas wrote, on 03 Jul 2019:
> > And again, that's an incompatible change for dash, ksh88, ksh93,
> > pdksh, mksh, bosh, yash where:
> >
> > a='\*'
> > ls -ld $a
> >
> > lists the files that start with \
>
> Which is inconsistent with find, pax, fnmatch() and
Stephane Chazelas wrote, on 03 Jul 2019:
>
> 2019-07-03 09:24:10 +0100, Geoff Clare:
> [...]
> > [...] If any character (ordinary, shell
> >special, or pattern special) is quoted or (where shell quoting is not
> >in effect) escaped with a , that pattern shall
Harald van Dijk wrote, on 02 Jul 2019:
>
> >>That's not because the word "unquoted" is used, which only applies to shell
> >>quoting, that's because 2.13.1 contains "All of the requirements and effects
> >>of quoting on ordinary, shell special, and special pattern characters shall
> >>apply to
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=1265
==
Reported By:geoffclare
Assigned To:
19 matches
Mail list logo
