From: Drew Adams <drew.adams@oracle.com>
To: emacsq <laszlomail@protonmail.com>, Juri Linkov <juri@linkov.net>
Cc: "54017@debbugs.gnu.org" <54017@debbugs.gnu.org>
Subject: bug#54017: [External] : bug#54017: add regexp translation option to read-regexp
Date: Sun, 20 Feb 2022 22:46:20 +0000 [thread overview]
Message-ID: <SJ0PR10MB54886B774B04ECA1AA6270AEF3399@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <Ye-sTBsBQ_V1mhMei3gAUe9obgszsnMbjNBs0VNYzPYusPbWon36ObiXpreX3dwOg1CKsTLFw4Y9iSoZFeyXcd-prJ5G1E3_rcxpIuypNy4=@protonmail.com>
(Probably at least somewhat off-topic.)
I'd like to see Emacs regexp handling support
a way to either (1) specify a new, multiline
"dot" syntax that's equivalent to \(.\|[\n]\)
or (2) have a (dynamic) variable, or a mode,
that you can toggle to switch the behavior of
ordinary dot to multiline dot.
___
In Icicles I have a command that toggles the
behavior in the minibuffer. Users see `.',
but under the covers \(.\|[\n]\) is used.
Editing (e.g. char deletion) automatically
treats that regexp as if it were just the
single char `.'.
When a `.' in the minibuffer actually stands
for \(.\|[\n]\) it gets highlighted, to
remind you of its behavior.
This is admittedly just a hack. It would be
much better for Emacs itself to provide for
multiline (i.e. true any-char) dot matching.
next prev parent reply other threads:[~2022-02-20 22:46 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
2022-02-20 22:46 ` Drew Adams [this message]
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=SJ0PR10MB54886B774B04ECA1AA6270AEF3399@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--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).