From: Jay Kamat <jaygkamat@gmail.com>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
lokedhs@gmail.com, emacs-devel@gnu.org,
"Philippe Vaucher" <philippe.vaucher@gmail.com>,
"Jay Kamat" <jaygkamat@gmail.com>, "Alan Mackenzie" <acm@muc.de>,
"Eli Zaretskii" <eliz@gnu.org>,
"Drew Adams" <drew.adams@oracle.com>
Subject: Re: modern regexes in emacs
Date: Fri, 15 Feb 2019 18:44:27 -0800 [thread overview]
Message-ID: <87r2c8jvuc.fsf@eve> (raw)
In-Reply-To: <20190215204652.6ebc1615@jabberwock.cb.piermont.com>
Perry E. Metzger writes:
> Other people get to pick what they want, too.
> If you don't want to let other people get the option of using
> the modern syntax, that's not demanding the right to use the old one,
> which won't be taken from you, that's demanding the right to keep
> other people from using the reasonable modern syntax. I think that's
> unreasonable.
I suppose you didn't read my previous mail past the first sentence, so I'll
quote it below for convenience:
>> I started using Emacs less than 4 years ago (so I could probably consider myself a 'modern user'), and I honestly find the new syntax much more confusing. I have never used the flags in those programs to get the new syntax, and I have seen those flags in a shrinking minority of shell scripts. I find the new syntax much more unreadable and arcane than the original, although the original is difficult by itself.
>>
>> I don't oppose adding more syntaxes, but I will never willingly use the new format personally.
Although, now that you've proposed it, a world where everyone must use rx does
sound very nice :).
I haven't read too much in the regexp code of Emacs, but it might be easier to
maintain one 'core' regexp language and translate 'alternative syntaxes' down
to some form of common representation. It would also be nice to provide some
facility for writing your own regexp flavor (Extended, Basic, Perl, Fixed,
<whatever's 'modern' in 50 years>) and integrating it into Emacs. Because of
that, I think it would be a good idea to make whatever interface used support
multiple possible flavors. I don't think that can easily be done with multiple
standalone functions (by itself). It would also be nice to have some facility
to pre 'compile' down to the intermediate representation ahead of time for
performance reasons (if it's not all implemented via macros like rx is).
-Jay
next prev parent reply other threads:[~2019-02-16 2:44 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 16:37 modern regexes in emacs Perry E. Metzger
2018-06-16 17:45 ` Radon Rosborough
2018-06-16 18:25 ` Perry E. Metzger
2018-06-16 21:01 ` Daniel Colascione
2018-06-16 22:31 ` Jay Kamat
2019-02-09 17:20 ` Philippe Vaucher
2019-02-10 9:39 ` Elias Mårtenson
2019-02-11 22:12 ` Mattias Engdegård
2019-02-15 13:42 ` Philippe Vaucher
2019-02-15 14:10 ` Clément Pit-Claudel
2019-02-15 15:03 ` Philippe Vaucher
2019-02-15 15:13 ` Clément Pit-Claudel
2019-02-15 14:18 ` Eli Zaretskii
2019-02-15 15:28 ` Perry E. Metzger
2019-02-15 16:06 ` Stefan Monnier
2019-02-15 16:24 ` Mattias Engdegård
2019-02-15 16:47 ` Perry E. Metzger
2019-02-15 17:54 ` Alan Mackenzie
2019-02-15 18:27 ` Drew Adams
2019-02-15 23:33 ` Perry E. Metzger
2019-02-16 0:34 ` Jay Kamat
2019-02-16 1:46 ` Perry E. Metzger
2019-02-16 2:44 ` Jay Kamat [this message]
2019-02-15 18:36 ` Eli Zaretskii
2019-02-15 18:43 ` Mattias Engdegård
2019-02-15 19:48 ` Eli Zaretskii
2019-02-17 3:17 ` Richard Stallman
2019-02-25 14:47 ` Lars Ingebrigtsen
2019-02-25 15:46 ` Clément Pit-Claudel
2019-02-26 2:57 ` Richard Stallman
2019-02-26 12:39 ` Lars Ingebrigtsen
2019-02-26 13:24 ` Troy Hinckley
2019-02-26 13:32 ` Lars Ingebrigtsen
2019-02-26 14:33 ` Andreas Schwab
2019-02-27 12:09 ` Mattias Engdegård
2019-02-27 18:18 ` Daniel Pittman
2019-02-26 15:29 ` Eli Zaretskii
2019-02-27 4:08 ` Richard Stallman
2019-02-26 3:47 ` Elias Mårtenson
2019-02-26 12:00 ` Mattias Engdegård
2019-02-15 23:35 ` Perry E. Metzger
2019-02-17 20:01 ` Juri Linkov
2019-02-18 0:38 ` Stefan Monnier
2019-02-15 18:46 ` Clément Pit-Claudel
2019-02-15 19:52 ` Eli Zaretskii
2019-02-15 20:08 ` Clément Pit-Claudel
2019-02-15 19:14 ` Alan Mackenzie
2019-02-15 20:00 ` Eli Zaretskii
2019-02-15 20:40 ` Alan Mackenzie
2019-02-15 23:33 ` Perry E. Metzger
2019-02-15 18:44 ` Clément Pit-Claudel
2019-02-15 19:37 ` Stefan Monnier
2019-02-19 12:29 ` Van L
2019-02-17 20:47 ` Stefan Monnier
2019-02-18 8:40 ` Philippe Vaucher
2019-02-18 8:55 ` Mattias Engdegård
-- strict thread matches above, loose matches on Subject: below --
2018-06-16 21:33 Jimmy Yuen Ho Wong
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=87r2c8jvuc.fsf@eve \
--to=jaygkamat@gmail.com \
--cc=acm@muc.de \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lokedhs@gmail.com \
--cc=mattiase@acm.org \
--cc=perry@piermont.com \
--cc=philippe.vaucher@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).