GNU bug report logs -
#76945
[PATCH] etags: character classes and intervals not working in --regex
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 76945 in the body.
You can then email your comments to 76945 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Tue, 11 Mar 2025 15:39:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Vladimir Gorsunov <gorsunov <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 11 Mar 2025 15:39:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Before commit d904cc83 regex syntax flags used in etags were
RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
that got changed to 0. Including a patch that restores
RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
to the test. As far I can understand from the bug 74861, the
absence of shy groups and non-greedy matching won't be fixed
until Gnulib supports them
[0001-etags-restore-some-regex-features-that-used-to-work-.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Tue, 11 Mar 2025 17:42:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 76945 <at> debbugs.gnu.org (full text, mbox):
> Date: Tue, 11 Mar 2025 14:28:45 +0200
> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
>
> Before commit d904cc83 regex syntax flags used in etags were
>
> RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
>
> that got changed to 0. Including a patch that restores
> RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
> to the test. As far I can understand from the bug 74861, the
> absence of shy groups and non-greedy matching won't be fixed
> until Gnulib supports them
Thanks.
Paul, any comments?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Tue, 11 Mar 2025 18:00:03 GMT)
Full text and
rfc822 format available.
Message #11 received at 76945 <at> debbugs.gnu.org (full text, mbox):
On 2025-03-11 10:41, Eli Zaretskii wrote:
>> Date: Tue, 11 Mar 2025 14:28:45 +0200
>> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
>>
>> Before commit d904cc83 regex syntax flags used in etags were
>>
>> RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
>>
>> that got changed to 0. Including a patch that restores
>> RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
>> to the test. As far I can understand from the bug 74861, the
>> absence of shy groups and non-greedy matching won't be fixed
>> until Gnulib supports them
>
> Thanks.
>
> Paul, any comments?
As I understand it the original design for glibc regex was that Emacs
was the default, so a flags value of zero meant Emacs. This is why
RE_SYNTAX_EMACS is 0.
Evidently that design goal no longer holds, so it makes sense to adjust
Emacs's use of glibc flags to match the behavior of Emacs's only
regular-expression implementation in emacs/src/regex-emacs.c as best we can.
However, surely this adjustment should be made in Gnulib, not in
etags.c. That is, gnulib/lib/regex.h (aka emacs/lib/regex.h) should
#define RE_SYNTAX_EMACS to equal RE_CHAR_CLASSES | RE_INTERVALS, not
zero. And eventually this change should be migrated back to glibc.
I'll cc this to rms in case he has further comments about this.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Tue, 11 Mar 2025 22:32:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 76945 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Excuse me but I have a question. If Gnulib is a collection of utility code
to be used by all projects, why is carrying something Emacs specific? Is
RE_SYNTAX_EMACS used by other projects?
On Tue, Mar 11, 2025 at 7:58 PM Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> On 2025-03-11 10:41, Eli Zaretskii wrote:
> >> Date: Tue, 11 Mar 2025 14:28:45 +0200
> >> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> >>
> >> Before commit d904cc83 regex syntax flags used in etags were
> >>
> >> RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
> >>
> >> that got changed to 0. Including a patch that restores
> >> RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
> >> to the test. As far I can understand from the bug 74861, the
> >> absence of shy groups and non-greedy matching won't be fixed
> >> until Gnulib supports them
> >
> > Thanks.
> >
> > Paul, any comments?
>
> As I understand it the original design for glibc regex was that Emacs
> was the default, so a flags value of zero meant Emacs. This is why
> RE_SYNTAX_EMACS is 0.
>
> Evidently that design goal no longer holds, so it makes sense to adjust
> Emacs's use of glibc flags to match the behavior of Emacs's only
> regular-expression implementation in emacs/src/regex-emacs.c as best we
> can.
>
> However, surely this adjustment should be made in Gnulib, not in
> etags.c. That is, gnulib/lib/regex.h (aka emacs/lib/regex.h) should
> #define RE_SYNTAX_EMACS to equal RE_CHAR_CLASSES | RE_INTERVALS, not
> zero. And eventually this change should be migrated back to glibc.
>
> I'll cc this to rms in case he has further comments about this.
>
--
Mit Respekt, Vladimir Gorsunov
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Tue, 11 Mar 2025 23:58:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 76945 <at> debbugs.gnu.org (full text, mbox):
On 3/11/25 15:30, Vladimir Gorsunov wrote:
> If Gnulib is a collection of utility code
> to be used by all projects, why is carrying something Emacs specific? Is
> RE_SYNTAX_EMACS used by other projects?
Zile (an Emacs clone) uses it, and it's used in higher-level libraries
that front for the GNU C library, e.g., [1].
[1]: https://github.com/jddurand/re-engine-GNU
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Sat, 29 Mar 2025 11:15:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 76945 <at> debbugs.gnu.org (full text, mbox):
Ping! Can we make some progress in resolving this?
Richard, do you have any comments?
> Date: Tue, 11 Mar 2025 10:58:58 -0700
> Cc: 76945 <at> debbugs.gnu.org, Richard Stallman <rms <at> gnu.org>,
> Vladimir Gorsunov <gorsunov <at> gmail.com>
> From: Paul Eggert <eggert <at> cs.ucla.edu>
>
> On 2025-03-11 10:41, Eli Zaretskii wrote:
> >> Date: Tue, 11 Mar 2025 14:28:45 +0200
> >> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> >>
> >> Before commit d904cc83 regex syntax flags used in etags were
> >>
> >> RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
> >>
> >> that got changed to 0. Including a patch that restores
> >> RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
> >> to the test. As far I can understand from the bug 74861, the
> >> absence of shy groups and non-greedy matching won't be fixed
> >> until Gnulib supports them
> >
> > Thanks.
> >
> > Paul, any comments?
>
> As I understand it the original design for glibc regex was that Emacs
> was the default, so a flags value of zero meant Emacs. This is why
> RE_SYNTAX_EMACS is 0.
>
> Evidently that design goal no longer holds, so it makes sense to adjust
> Emacs's use of glibc flags to match the behavior of Emacs's only
> regular-expression implementation in emacs/src/regex-emacs.c as best we can.
>
> However, surely this adjustment should be made in Gnulib, not in
> etags.c. That is, gnulib/lib/regex.h (aka emacs/lib/regex.h) should
> #define RE_SYNTAX_EMACS to equal RE_CHAR_CLASSES | RE_INTERVALS, not
> zero. And eventually this change should be migrated back to glibc.
>
> I'll cc this to rms in case he has further comments about this.
>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Fri, 11 Apr 2025 16:56:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 76945 <at> debbugs.gnu.org (full text, mbox):
Made a patch to gnulib
https://lists.gnu.org/archive/html/bug-gnulib/2025-04/msg00064.html as
Paul suggested
On 3/29/25 13:14, Eli Zaretskii wrote:
> Ping! Can we make some progress in resolving this?
>
> Richard, do you have any comments?
>
>> Date: Tue, 11 Mar 2025 10:58:58 -0700
>> Cc: 76945 <at> debbugs.gnu.org, Richard Stallman <rms <at> gnu.org>,
>> Vladimir Gorsunov <gorsunov <at> gmail.com>
>> From: Paul Eggert <eggert <at> cs.ucla.edu>
>>
>> On 2025-03-11 10:41, Eli Zaretskii wrote:
>>>> Date: Tue, 11 Mar 2025 14:28:45 +0200
>>>> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
>>>>
>>>> Before commit d904cc83 regex syntax flags used in etags were
>>>>
>>>> RE_CHAR_CLASSES | RE_INTERVALS | RE_SHY_GROUPS | RE_FRUGAL
>>>>
>>>> that got changed to 0. Including a patch that restores
>>>> RE_CHAR_CLASSES and RE_INTERVALS and adds check for these features
>>>> to the test. As far I can understand from the bug 74861, the
>>>> absence of shy groups and non-greedy matching won't be fixed
>>>> until Gnulib supports them
>>> Thanks.
>>>
>>> Paul, any comments?
>> As I understand it the original design for glibc regex was that Emacs
>> was the default, so a flags value of zero meant Emacs. This is why
>> RE_SYNTAX_EMACS is 0.
>>
>> Evidently that design goal no longer holds, so it makes sense to adjust
>> Emacs's use of glibc flags to match the behavior of Emacs's only
>> regular-expression implementation in emacs/src/regex-emacs.c as best we can.
>>
>> However, surely this adjustment should be made in Gnulib, not in
>> etags.c. That is, gnulib/lib/regex.h (aka emacs/lib/regex.h) should
>> #define RE_SYNTAX_EMACS to equal RE_CHAR_CLASSES | RE_INTERVALS, not
>> zero. And eventually this change should be migrated back to glibc.
>>
>> I'll cc this to rms in case he has further comments about this.
>>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Sun, 13 Apr 2025 09:56:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 76945 <at> debbugs.gnu.org (full text, mbox):
> Date: Fri, 11 Apr 2025 19:55:01 +0300
> Cc: 76945 <at> debbugs.gnu.org
> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
>
> Made a patch to gnulib
> https://lists.gnu.org/archive/html/bug-gnulib/2025-04/msg00064.html as
> Paul suggested
Thanks. I guess we can now close this bug, as the issue will be
resolved in Gnulib?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Sun, 13 Apr 2025 11:09:04 GMT)
Full text and
rfc822 format available.
Message #29 received at 76945 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Seems strange to me to close before we make sure the software does, in
fact, behave as expected. But if that's how it is usually done in this
project, then of course!
On Sun, Apr 13, 2025 at 12:55 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > Date: Fri, 11 Apr 2025 19:55:01 +0300
> > Cc: 76945 <at> debbugs.gnu.org
> > From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> >
> > Made a patch to gnulib
> > https://lists.gnu.org/archive/html/bug-gnulib/2025-04/msg00064.html as
> > Paul suggested
>
> Thanks. I guess we can now close this bug, as the issue will be
> resolved in Gnulib?
>
--
Mit Respekt, Vladimir Gorsunov
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Sun, 13 Apr 2025 11:30:05 GMT)
Full text and
rfc822 format available.
Message #32 received at 76945 <at> debbugs.gnu.org (full text, mbox):
> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> Date: Sun, 13 Apr 2025 14:08:06 +0300
> Cc: eggert <at> cs.ucla.edu, rms <at> gnu.org, 76945 <at> debbugs.gnu.org
>
> Seems strange to me to close before we make sure the software does, in fact, behave as expected. But if
> that's how it is usually done in this project, then of course!
We could wait until Gnulib folks resolve this on their end, but
someone will need to tell us when that happens, because I don't
normally read the Gnulib list.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Sun, 13 Apr 2025 11:34:05 GMT)
Full text and
rfc822 format available.
Message #35 received at 76945 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I'll tell you
On Sun, Apr 13, 2025 at 2:29 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> > Date: Sun, 13 Apr 2025 14:08:06 +0300
> > Cc: eggert <at> cs.ucla.edu, rms <at> gnu.org, 76945 <at> debbugs.gnu.org
> >
> > Seems strange to me to close before we make sure the software does, in
> fact, behave as expected. But if
> > that's how it is usually done in this project, then of course!
>
> We could wait until Gnulib folks resolve this on their end, but
> someone will need to tell us when that happens, because I don't
> normally read the Gnulib list.
>
--
Mit Respekt, Vladimir Gorsunov
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Mon, 14 Apr 2025 12:13:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 76945 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Well, gnulib did fix the value. Thanks Paul. When I rebuilt etags after
running merge-gnulib, it worked as expected. Don't know if that warrants
criteria for closing. Of course someone still needs to commit updated
gnulib here for it to be fixed for everyone
On Sun, Apr 13, 2025 at 2:33 PM Vladimir Gorsunov <gorsunov <at> gmail.com>
wrote:
> I'll tell you
>
> On Sun, Apr 13, 2025 at 2:29 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>> > From: Vladimir Gorsunov <gorsunov <at> gmail.com>
>> > Date: Sun, 13 Apr 2025 14:08:06 +0300
>> > Cc: eggert <at> cs.ucla.edu, rms <at> gnu.org, 76945 <at> debbugs.gnu.org
>> >
>> > Seems strange to me to close before we make sure the software does, in
>> fact, behave as expected. But if
>> > that's how it is usually done in this project, then of course!
>>
>> We could wait until Gnulib folks resolve this on their end, but
>> someone will need to tell us when that happens, because I don't
>> normally read the Gnulib list.
>>
>
>
> --
> Mit Respekt, Vladimir Gorsunov
>
--
Mit Respekt, Vladimir Gorsunov
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76945
; Package
emacs
.
(Mon, 14 Apr 2025 13:41:01 GMT)
Full text and
rfc822 format available.
Message #41 received at 76945 <at> debbugs.gnu.org (full text, mbox):
> From: Vladimir Gorsunov <gorsunov <at> gmail.com>
> Date: Mon, 14 Apr 2025 15:11:43 +0300
> Cc: eggert <at> cs.ucla.edu, rms <at> gnu.org, 76945 <at> debbugs.gnu.org
>
> Well, gnulib did fix the value. Thanks Paul. When I rebuilt etags after running merge-gnulib, it worked as
> expected. Don't know if that warrants criteria for closing. Of course someone still needs to commit updated
> gnulib here for it to be fixed for everyone
Thanks. I think we will close this bug when Gnulib is updated in our
repository.
Reply sent
to
Paul Eggert <eggert <at> cs.ucla.edu>
:
You have taken responsibility.
(Sun, 20 Apr 2025 05:43:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Vladimir Gorsunov <gorsunov <at> gmail.com>
:
bug acknowledged by developer.
(Sun, 20 Apr 2025 05:43:03 GMT)
Full text and
rfc822 format available.
Message #46 received at 76945-done <at> debbugs.gnu.org (full text, mbox):
On 2025-04-14 06:39, Eli Zaretskii wrote:
> I think we will close this bug when Gnulib is updated in our
> repository.
I did that and am closing this bug report.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 18 May 2025 11:24:11 GMT)
Full text and
rfc822 format available.
This bug report was last modified 31 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.