From: Richard Stallman <rms@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: laszlomail@protonmail.com, larsi@gnus.org, 52558@debbugs.gnu.org
Subject: bug#52558: Option for easier typing of regexps
Date: Tue, 21 Dec 2021 23:16:17 -0500 [thread overview]
Message-ID: <E1mzt33-0004rr-N0@fencepost.gnu.org> (raw)
In-Reply-To: <0cac11c8-78c2-5625-d023-cda3bd4d7c9c@gmail.com> (message from Jim Porter on Mon, 20 Dec 2021 11:46:32 -0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I've attempted to resolve this issue in the other direction in
> Urgrep[1], which provides a unified way of running all these recursive
> grep-like tools. Specifically, it defaults to accepting BRE syntax and
> then, if the tool only accepts ERE/PCRE, it converts the BRE input into
> ERE/PCRE. That's not perfect either since then you end up in a situation
> where to use PCRE features, you have to enter them in a BRE-like syntax,
> which I find pretty confusing too. (This behavior is customizable in
> Urgrep, so if you like ERE/PCRE, you can set those as the input syntax.)
I think it would be a big step forward if we could do something along
these lines in Emacs. The details may be tricky, though.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-12-22 4:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 17:41 bug#52558: Option for easier typing of regexps ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-17 10:07 ` Phil Sainty
2021-12-18 16:47 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-18 4:41 ` Richard Stallman
2021-12-19 11:56 ` Lars Ingebrigtsen
2021-12-19 13:03 ` Phil Sainty
2021-12-19 14:08 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 16:11 ` Phil Sainty
2021-12-19 15:10 ` Michael Heerdegen
2021-12-20 4:43 ` Richard Stallman
2021-12-20 19:46 ` Jim Porter
2021-12-22 4:16 ` Richard Stallman [this message]
2021-12-19 17:01 ` Juri Linkov
2021-12-19 17:39 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 17:52 ` Juri Linkov
2021-12-19 17:57 ` Juri Linkov
2021-12-19 18:38 ` Juri Linkov
2021-12-19 18:48 ` Juri Linkov
2021-12-28 19:15 ` Juri Linkov
2021-12-28 20:21 ` Eli Zaretskii
2021-12-28 20:25 ` Juri Linkov
2021-12-28 20:35 ` Eli Zaretskii
2021-12-28 20:51 ` Juri Linkov
2021-12-29 12:32 ` Eli Zaretskii
2021-12-29 17:17 ` Juri Linkov
2021-12-29 18:25 ` Eli Zaretskii
2022-01-22 14:23 ` Lars Ingebrigtsen
2022-01-22 19:01 ` Juri Linkov
2022-01-23 12:36 ` Lars Ingebrigtsen
2022-01-23 18:09 ` Juri Linkov
2022-01-23 18:29 ` Lars Ingebrigtsen
2022-01-24 18:46 ` Juri Linkov
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=E1mzt33-0004rr-N0@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=52558@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.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).