From: emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 54017@debbugs.gnu.org
Subject: bug#54017: add regexp translation option to read-regexp
Date: Sun, 20 Feb 2022 19:06:53 +0000 [thread overview]
Message-ID: <Ye-sTBsBQ_V1mhMei3gAUe9obgszsnMbjNBs0VNYzPYusPbWon36ObiXpreX3dwOg1CKsTLFw4Y9iSoZFeyXcd-prJ5G1E3_rcxpIuypNy4=@protonmail.com> (raw)
In-Reply-To: <86r181lb1g.fsf@mail.linkov.net>
> 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).
If we wait for those complete translation functions then we
might have to wait for a long time, unless there are people
who want complete translations right now, but there were no
such volunteers in this thread for that task.
Adding an option for a custom translation function solves the
problem right know, everyone can change the symbols they are
most annoyed by and this function can be the base mechanism
for complete translations later if someone ever wants to do
those.
next prev parent reply other threads:[~2022-02-20 19:06 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 [this message]
2022-02-20 20:02 ` Eli Zaretskii
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='Ye-sTBsBQ_V1mhMei3gAUe9obgszsnMbjNBs0VNYzPYusPbWon36ObiXpreX3dwOg1CKsTLFw4Y9iSoZFeyXcd-prJ5G1E3_rcxpIuypNy4=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=54017@debbugs.gnu.org \
--cc=eliz@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).