On Sat, Apr 17, 2004 at 10:44:27PM +0200, Kurt Roeckx wrote:
If I understand Herbert Xu correctly, he's saying the regex
should be written as:
*[][~#$^*(){}\|;?]*
No, the way it's written currently is fine.
It's glibc's fnmatch(3) implementation that's broken.
Cheers,
--
Debian GNU/Linux
Kurt Roeckx [EMAIL PROTECTED] wrote:
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
You mean fnmatch() gets called with the FNM_NOESCAPE flag?
No. I mean that on the input path to fnmatch(), the escape characters
have to be there.
--
Debian
On Sat, Apr 17, 2004 at 10:44:27PM +0200, Kurt Roeckx wrote:
If I understand Herbert Xu correctly, he's saying the regex
should be written as:
*[][~#$^*(){}\|;?]*
No, the way it's written currently is fine.
It's glibc's fnmatch(3) implementation that's broken.
Cheers,
--
Debian GNU/Linux
Kurt Roeckx [EMAIL PROTECTED] wrote:
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
You mean fnmatch() gets called with the FNM_NOESCAPE flag?
No. I mean that on the input path to fnmatch(), the escape characters
have to be there.
--
Debian
On Sat, Apr 17, 2004 at 12:14:39PM -0700, Ben Pfaff wrote:
Herbert Xu [EMAIL PROTECTED] writes:
Accordingly, I believe that the pattern in your example means
backslash, followed by a, followed by closing square bracket, not what
you think it means.
You're quite right. This is
Herbert Xu [EMAIL PROTECTED] writes:
Accordingly, I believe that the pattern in your example means
backslash, followed by a, followed by closing square bracket, not what
you think it means.
You're quite right. This is reaffirmed by the POSIX document for
basic regular expressions, which is
On Sat, Apr 17, 2004 at 12:14:39PM -0700, Ben Pfaff wrote:
Herbert Xu [EMAIL PROTECTED] writes:
Accordingly, I believe that the pattern in your example means
backslash, followed by a, followed by closing square bracket, not what
you think it means.
You're quite right. This is
On Fri, Apr 16, 2004 at 12:54:03PM +1000, Herbert Xu wrote:
On Fri, Apr 16, 2004 at 08:09:05AM +1000, herbert wrote:
On Thu, Apr 15, 2004 at 03:10:58PM +0100, Colin Watson wrote:
Accordingly, I believe that the pattern in your example means
backslash, followed by a, followed by
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
After reading all that you have to get confused about what [\[\]\\] means.
At the highest level it says that the '\' should be discarded,
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
--
On Sat, Apr 17, 2004 at 07:58:21AM +1000, Herbert Xu wrote:
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
After reading all that you have to get confused about what [\[\]\\] means.
At the highest level it says that the '\' should be discarded,
Not quite. In the context of
Processing commands for [EMAIL PROTECTED]:
reopen 243885
Bug#243885: fnmatch breaks on [\]]
Bug reopened, originator not changed.
reassign 240887 dash
Bug#240887: backslashes are literal in shell bracket expressions
Bug reassigned from package `tetex-bin' to `dash'.
retitle 240887 fnmatch(3)
On Fri, Apr 16, 2004 at 12:54:03PM +1000, Herbert Xu wrote:
On Fri, Apr 16, 2004 at 08:09:05AM +1000, herbert wrote:
On Thu, Apr 15, 2004 at 03:10:58PM +0100, Colin Watson wrote:
Accordingly, I believe that the pattern in your example means
backslash, followed by a, followed by
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
After reading all that you have to get confused about what [\[\]\\] means.
At the highest level it says that the '\' should be discarded,
Not quite. In the context of case patterns and fnmatch, quote removal
is not performed.
--
On Sat, Apr 17, 2004 at 07:58:21AM +1000, Herbert Xu wrote:
On Fri, Apr 16, 2004 at 08:49:14PM +0200, Kurt Roeckx wrote:
After reading all that you have to get confused about what [\[\]\\] means.
At the highest level it says that the '\' should be discarded,
Not quite. In the context of
clone 240887 -1
retitle -1 fnmatch breaks on [\]]
submitter -1 [EMAIL PROTECTED]
reassign -1 libc6
tags 240887 pending
quit
On Wed, Apr 14, 2004 at 01:59:01PM +0200, Frank K?ster wrote:
This is how dash calls it in _some_ subdirectories:
configuring in tetex
running /bin/sh ./configure
Processing commands for [EMAIL PROTECTED]:
clone 240887 -1
Bug#240887: dash expands variable between '...'
Bug 240887 cloned as bug 243885.
retitle -1 fnmatch breaks on [\]]
Bug#243885: dash expands variable between '...'
Changed Bug title.
submitter -1 [EMAIL PROTECTED]
Bug#243885: fnmatch
On Thu, Apr 15, 2004 at 09:40:05PM +1000, Herbert Xu wrote:
On Wed, Apr 14, 2004 at 01:59:01PM +0200, Frank K?ster wrote:
This is how dash calls it in _some_ subdirectories:
configuring in tetex
running /bin/sh ./configure --prefix=/usr --enable-ipc --without-dialog\
Processing commands for [EMAIL PROTECTED]:
reopen 243885
Bug#243885: fnmatch breaks on [\]]
Bug reopened, originator not changed.
reassign 240887 dash
Bug#240887: backslashes are literal in shell bracket expressions
Bug reassigned from package `tetex-bin' to `dash'.
retitle 240887 fnmatch(3)
clone 240887 -1
retitle -1 fnmatch breaks on [\]]
submitter -1 [EMAIL PROTECTED]
reassign -1 libc6
tags 240887 pending
quit
On Wed, Apr 14, 2004 at 01:59:01PM +0200, Frank K?ster wrote:
This is how dash calls it in _some_ subdirectories:
configuring in tetex
running /bin/sh ./configure
Processing commands for [EMAIL PROTECTED]:
clone 240887 -1
Bug#240887: dash expands variable between '...'
Bug 240887 cloned as bug 243885.
retitle -1 fnmatch breaks on [\]]
Bug#243885: dash expands variable between '...'
Changed Bug title.
submitter -1 [EMAIL PROTECTED]
Bug#243885: fnmatch
On Thu, Apr 15, 2004 at 09:40:05PM +1000, Herbert Xu wrote:
On Wed, Apr 14, 2004 at 01:59:01PM +0200, Frank K?ster wrote:
This is how dash calls it in _some_ subdirectories:
configuring in tetex
running /bin/sh ./configure --prefix=/usr --enable-ipc --without-dialog\
reopen 243885
reassign 240887 dash
retitle 240887 fnmatch(3) is broken
quit
On Fri, Apr 16, 2004 at 08:09:05AM +1000, herbert wrote:
On Thu, Apr 15, 2004 at 03:10:58PM +0100, Colin Watson wrote:
Accordingly, I believe that the pattern in your example means
backslash, followed by a,
22 matches
Mail list logo
