From: Eli Zaretskii <eliz@gnu.org>
To: emacsq <laszlomail@protonmail.com>
Cc: 54017@debbugs.gnu.org, juri@linkov.net
Subject: bug#54017: add regexp translation option to read-regexp
Date: Sun, 20 Feb 2022 22:02:27 +0200 [thread overview]
Message-ID: <837d9pwbl8.fsf@gnu.org> (raw)
In-Reply-To: <Ye-sTBsBQ_V1mhMei3gAUe9obgszsnMbjNBs0VNYzPYusPbWon36ObiXpreX3dwOg1CKsTLFw4Y9iSoZFeyXcd-prJ5G1E3_rcxpIuypNy4=@protonmail.com> (message from emacsq on Sun, 20 Feb 2022 19:06:53 +0000)
> Date: Sun, 20 Feb 2022 19:06:53 +0000
> From: emacsq <laszlomail@protonmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 54017@debbugs.gnu.org
>
> > Then need to wait when someone will step forward to write these
> > BRE/ERE/PCRE translation functions.
>
> This is a bigger job and is there a current need for it?
>
> People just want to make their life easier and change the way
> how the syntax of some of the symbols often used by them works
> in interactive input (e.g. grouping).
Like I said: I don't think we should support arbitrary
transformations of regular expressions' syntax. It makes no sense to
me.
And we don't need to support _all_ of the above syntaxes, we could
support just the BRE or just the ERE.
next prev parent reply other threads:[~2022-02-20 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 20:21 bug#54017: add regexp translation option to read-regexp emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-16 18:25 ` Juri Linkov
2022-02-16 19:28 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 8:24 ` Juri Linkov
2022-02-17 9:09 ` Juri Linkov
2022-02-17 9:18 ` Eli Zaretskii
2022-02-17 10:04 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 17:40 ` Juri Linkov
2022-02-20 19:06 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-20 20:02 ` Eli Zaretskii [this message]
2022-02-20 22:46 ` bug#54017: [External] : " Drew Adams
2022-02-17 10:55 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=837d9pwbl8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54017@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).