unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, ndame <laszlomail@protonmail.com>
Cc: 52558@debbugs.gnu.org
Subject: bug#52558: Option for easier typing of regexps
Date: Mon, 20 Dec 2021 11:46:32 -0800	[thread overview]
Message-ID: <0cac11c8-78c2-5625-d023-cda3bd4d7c9c@gmail.com> (raw)
In-Reply-To: <87o85cvmek.fsf@gnus.org>

On 12/19/2021 3:56 AM, Lars Ingebrigtsen wrote:
> I think it would be really confusing to have a different regexp syntax
> when prompting interactively to when you're writing code, so I don't
> think this would be a good idea.  Anybody else have a different opinion?

I think this depends on how people use Emacs. While there's definitely 
some potential for confusion if you switch between entering Emacs 
regexps interactively or by writing Elisp, there's also potential for 
confusion if you often write regexps for external tools from Emacs. For 
example, if you use one of the "modern" recursive grep-like tools (ack, 
ag, ripgrep, etc), most of them use PCRE syntax (or something close to 
PCRE). It's easy to forget that Isearch uses BRE but your preferred 
rgrep-like tool uses ERE/PCRE.

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'm not sure this makes the decision about what to do any easier though. 
In fact, it probably just muddies the waters further. :)

[1] https://github.com/jimporter/urgrep





  parent reply	other threads:[~2021-12-20 19:46 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 [this message]
2021-12-22  4:16     ` Richard Stallman
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=0cac11c8-78c2-5625-d023-cda3bd4d7c9c@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=52558@debbugs.gnu.org \
    --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).