A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=247
==
Reported By:dwheeler
Assigned To:
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=247
==
Reported By:dwheeler
Assigned To:
On 24/09/2019 15:32, Geoff Clare wrote:
Harald van Dijk wrote, on 24 Sep 2019:
There is a reason I wrote "in its current version". I do not think it is
reasonable to describe bash 4 behaviour that had already been changed when
this was being discussed as "existing practice".
Bash 3 on macOS
2019-09-24 15:53:07 +0100, Geoff Clare:
[...]
> to:
>
> 3. If a specified pattern contains any '*', '?' or '[' characters
>that will be treated as special (see [xref to 2.13.1]), it shall
>be matched against existing filenames and pathnames, as
>appropriate. Each
Stephane Chazelas wrote, on 24 Sep 2019:
>
> In:
>
> */x, the shell only needs search access to all the directories
> in the current directory (it will typically attempt a
> lstat(dir/x) for each of them. (And you need search and read
> access to the current directory)
>
> In x/*, you need
what is happening with the action to update the syncronisation plan about the
revision
of posix? it seems to be not even mentioned in the meeting. Please refer to the
sc22
resolution, I have prevously sent you.
best regards
keld
On Tue, Sep 24, 2019 at 10:06:31AM +0100, Andrew Josey wrote:
>
A NOTE has been added to this issue.
==
http://www.austingroupbugs.net/view.php?id=247
==
Reported By:dwheeler
Assigned To:
Harald van Dijk wrote, on 24 Sep 2019:
>
> On 24/09/2019 12:24, Geoff Clare wrote:
> >Harald van Dijk wrote, on 24 Sep 2019:
> >>
> >>>2. Existing practice in most shells that do treat backslash as special in
> >>>"indirect" patterns in pathname expansions is only to match patterns
> >>>against
2019-09-24 12:24:43 +0100, Geoff Clare:
[...]
> > In NetBSD sh, backslash is given this special treatment only if the current
> > pathname component of the pattern includes a metacharacter. That is, an
> > indirect /de\v/nul[l] does not find /dev/null, but an indirect /d[e]\v/null
> > does.
>
>
2019-09-24 09:46:27 +0100, Geoff Clare:
[...]
> > Regardless, the above question applies in
> >
[...]
> var='\*'
[...]
> > printf '%s\n' */$var
> >
> > Or
> >
> > printf '%s\n' $var/*
>
> Those both have a * that will be treated as special, so matching
> against existing files is performed. The
On 24/09/2019 12:24, Geoff Clare wrote:
Harald van Dijk wrote, on 24 Sep 2019:
2. Existing practice in most shells that do treat backslash as special in
"indirect" patterns in pathname expansions is only to match patterns
against existing pathnames if the pattern includes a '*', '?' or '['
Harald van Dijk wrote, on 24 Sep 2019:
>
> >2. Existing practice in most shells that do treat backslash as special in
> >"indirect" patterns in pathname expansions is only to match patterns
> >against existing pathnames if the pattern includes a '*', '?' or '[' that
> >is treated as special.
On 23/09/2019 16:39, Austin Group Bug Tracker wrote:
[...]
--
(0004564) geoffclare (manager) - 2019-09-23 15:39
http://austingroupbugs.net/view.php?id=1234#c4564
All
Enclosed are the minutes of yesterdays call
regards
Andrew
Minutes of the 23 September 2019 Teleconference Austin-970 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 24th September 2019
Attendees:
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The
The following issue has been UPDATED.
==
http://austingroupbugs.net/view.php?id=985
==
Reported By:rhansen
Assigned To:
Dear all
Please note that the interpretation for this bug has been revised and the 30
day review is being restarted
985 Shell and Utilities quote removal missing from case statement
patterns and alternative expansions
Comments are due not later than October 24 2019
regards
Andrew
Stephane Chazelas wrote, on 24 Sep 2019:
>
> 2019-09-23 15:39:49 +, Austin Group Bug Tracker:
> [...]
> > On page 2384 line 76271 section 2.13.3, change:3. Specified
> > patterns shall be matched against existing filenames and pathnames, as
> > appropriate.to:3. If a specified pattern
2019-09-23 15:39:49 +, Austin Group Bug Tracker:
[...]
> On page 2384 line 76271 section 2.13.3, change:3. Specified
> patterns shall be matched against existing filenames and pathnames, as
> appropriate.to:3. If a specified pattern contains
> any '*', '?' or '[' characters that will be
18 matches
Mail list logo
