From: Paul Eggert <eggert@cs.ucla.edu>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 64128@debbugs.gnu.org
Subject: bug#64128: regexp parser zero-width assertion bugs
Date: Tue, 20 Jun 2023 23:08:38 -0700 [thread overview]
Message-ID: <6c9a05a6-d1a1-7e12-0834-16bf9f539fb1@cs.ucla.edu> (raw)
In-Reply-To: <9F76C15B-0038-4DFE-B2DE-F35EC1D87C93@gmail.com>
On 2023-06-20 04:36, Mattias Engdegård wrote:
> Sounds fine, with the option to go full error on group B if we agree that that's even better.
That would be fine too. I'd even prefer it. In the meantime your patch
looks good.
> I still think the whole chapter needs a reform from the sheer weight of organic growth over the years. In particular, the division between "regexp special" and "regexp backslash" is purely syntactical, not semantic, and groups things in the wrong way.
Agreed.
next prev parent reply other threads:[~2023-06-21 6:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 12:20 bug#64128: regexp parser zero-width assertion bugs Mattias Engdegård
2023-06-17 18:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 20:07 ` Mattias Engdegård
2023-06-17 22:18 ` Paul Eggert
2023-06-18 4:55 ` Eli Zaretskii
2023-06-18 20:26 ` Mattias Engdegård
2023-06-19 3:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-19 8:44 ` Mattias Engdegård
2023-06-19 12:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-19 18:34 ` Mattias Engdegård
2023-06-19 19:21 ` Paul Eggert
2023-06-19 19:52 ` Mattias Engdegård
2023-06-19 20:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-20 11:36 ` Mattias Engdegård
2023-06-21 6:08 ` Paul Eggert [this message]
2023-06-21 15:57 ` Mattias Engdegård
2023-06-19 20:40 ` Paul Eggert
2023-06-19 18:14 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c9a05a6-d1a1-7e12-0834-16bf9f539fb1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=64128@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.