From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: mattias.engdegard@gmail.com, monnier@iro.umontreal.ca,
64128@debbugs.gnu.org
Subject: bug#64128: regexp parser zero-width assertion bugs
Date: Sun, 18 Jun 2023 07:55:01 +0300 [thread overview]
Message-ID: <83pm5tpdy2.fsf@gnu.org> (raw)
In-Reply-To: <a4a870b6-b637-7e61-0b18-7fa01b970a4f@cs.ucla.edu> (message from Paul Eggert on Sat, 17 Jun 2023 15:18:00 -0700)
> Cc: 64128@debbugs.gnu.org
> Date: Sat, 17 Jun 2023 15:18:00 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> > Clearly, but some behaviour needs to be preserved for compatibility.
> > Regexps like "^*" aren't uncommon. Can it be generalised in a useful way?
> >
>
> doc/lispref/searching.texi says that "*" is treated as an ordinary
> character if it is in a context where its special meaning makes no
> sense, giving "*foo" as an example. If we break with this tradition by
> making "\b*" an error instead of being equivalent to "\b\*", we should
> update that part of the manual.
>
> One possible way forward is to update doc/lispref/searching.texi to
> specify what we want. Then we can modify the code to match the updated
> documentation.
>
> In my experience, modifying the doc is often the hard part, so I took a
> crack at that in the draft proposed patch, which I have not installed.
>
> Comments?
My comment is that since this was a documented feature, I'm not
interested in making it an error.
next prev parent reply other threads:[~2023-06-18 4:55 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 [this message]
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
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=83pm5tpdy2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64128@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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.