From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>,
stefankangas@gmail.com, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Ugly regexps
Date: Thu, 4 Mar 2021 12:25:48 +0100 [thread overview]
Message-ID: <E0FAE627-A3AC-4A45-B632-FEF0DB5DB07C@acm.org> (raw)
In-Reply-To: <87lfb3w5v7.fsf@gnus.org>
4 mars 2021 kl. 11.49 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> I think users will be very happy to be able to use the regexp syntax
> they know (instead of the special Emacs regexp variants) in their .emacs
> files.
Unfortunately it isn't the regexp syntax they know; it's a new variant, with subtle differences from what they may think it is. False friends include [] \d \s \w . ^ $ and so on: constructs that look like something they know well from other software but that have slightly (or completely) different meaning in Emacs.
This doesn't mean that `ere` wouldn't be a useful addition, but that it should not be presented as "Regexps just like in Python (etc)! No Emacs quirks to worry about!" but exactly for what it is: a way to toggle the requirement for backslash-escaping (){}|, no more and no less. Someone who wants to write or understand an `ere` regexp has to read the Emacs regexp docs, then the `ere` documentation, and then mentally combine the two.
next prev parent reply other threads:[~2021-03-04 11:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 0:32 Ugly regexps Stefan Monnier
2021-03-03 1:32 ` Stefan Kangas
2021-03-03 2:08 ` Stefan Kangas
2021-03-03 6:19 ` Eli Zaretskii
2021-03-03 20:46 ` Alan Mackenzie
2021-03-04 18:35 ` Stefan Kangas
2021-03-03 6:00 ` Eli Zaretskii
2021-03-03 15:46 ` Stefan Monnier
2021-03-03 16:30 ` Eli Zaretskii
2021-03-03 17:44 ` Stefan Monnier
2021-03-03 18:46 ` Stefan Kangas
2021-03-03 19:21 ` Eli Zaretskii
2021-03-03 19:50 ` Stefan Kangas
2021-03-03 20:16 ` Stefan Kangas
2021-03-03 19:50 ` Stefan Kangas
2021-03-03 19:58 ` Dmitry Gutov
2021-03-03 20:07 ` [External] : " Drew Adams
2021-03-03 20:31 ` Stefan Kangas
2021-03-03 22:17 ` Drew Adams
2021-03-03 22:32 ` Stefan Monnier
2021-03-03 20:32 ` Stefan Monnier
2021-03-04 5:47 ` Eli Zaretskii
2021-03-04 10:49 ` Lars Ingebrigtsen
2021-03-04 11:25 ` Mattias Engdegård [this message]
2021-03-04 11:28 ` Alan Mackenzie
2021-03-04 14:11 ` Eli Zaretskii
2021-03-04 14:25 ` Dmitry Gutov
2021-03-04 14:50 ` tomas
2021-03-04 15:04 ` Dmitry Gutov
2021-03-05 5:45 ` Richard Stallman
2021-03-05 11:47 ` Dmitry Gutov
2021-03-06 5:11 ` Richard Stallman
2021-03-04 15:05 ` Dmitry Gutov
2021-03-04 15:11 ` Eli Zaretskii
2021-03-03 19:32 ` [External] : " Drew Adams
2021-03-03 7:09 ` Helmut Eller
2021-03-03 14:11 ` Stefan Kangas
2021-03-03 16:40 ` Stefan Monnier
2021-03-03 15:49 ` Stefan Monnier
2021-03-03 12:17 ` Dmitry Gutov
2021-03-03 15:48 ` Stefan Monnier
2021-03-03 13:57 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E0FAE627-A3AC-4A45-B632-FEF0DB5DB07C@acm.org \
--to=mattiase@acm.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).