From: emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 54017@debbugs.gnu.org
Subject: bug#54017: add regexp translation option to read-regexp
Date: Tue, 15 Feb 2022 20:21:35 +0000 [thread overview]
Message-ID: <pml_I1y3BHYiUQCE1X45lx3leJ8mMRTwOclJd1qV7BDsVLjchfTfiqBFA4VwpHZACnp5pQmyPcD2biU-MEeM1tm9rURQhGuslCqCt3bWZAg=@protonmail.com> (raw)
Suppose, the user wants to use ( ) for capturing and
\( \) for matching parens. He provides a function
which does this translation.
If this new option is set and is a function which does
the translation then read-regexp will
- accept the format which the user prefers, in this case
( ... ) for capturing.
- store regexps in this format in history, so the user
can work with the user's preferred format even when
retrieving history entries.
- return the elisp format regexp by calling the function
provided by the user which does the translation.
next reply other threads:[~2022-02-15 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 20:21 emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-16 18:25 ` bug#54017: add regexp translation option to read-regexp 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
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='pml_I1y3BHYiUQCE1X45lx3leJ8mMRTwOclJd1qV7BDsVLjchfTfiqBFA4VwpHZACnp5pQmyPcD2biU-MEeM1tm9rURQhGuslCqCt3bWZAg=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=54017@debbugs.gnu.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).