From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Cc: "monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Ugly regexps
Date: Wed, 3 Mar 2021 20:07:07 +0000 [thread overview]
Message-ID: <SA2PR10MB4474984EB823D12933574DEEF3989@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <96182b13-f921-6f91-0cdc-320f54ed16bf@yandex.ru>
> > And ERE isn't?
>
> To be fair, extended regular expressions are the regular expressions
> flavor most commonly used in the contemporary world, recent/popular
> programming languages, etc.
>
> So for a lot of people this won't be +1 thing to learn.
See my previous message. It _will_ be a +1 to learn,
in the context of Emacs, if people have to also learn
the Elisp syntax anyway, for interactive use.
Any way you look at it, I think, if the Elisp regexp
syntax is what is used interactively (modulo extra
backslashing), then adding another syntax means that
using that other syntax is a +1 - extra learning.
Not that extra learning is necessarily bad... ;-)
next prev parent reply other threads:[~2021-03-03 20:07 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 ` Drew Adams [this message]
2021-03-03 20:31 ` [External] : " 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
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=SA2PR10MB4474984EB823D12933574DEEF3989@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).