From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: VanL <van@scratch.space>, 31953@debbugs.gnu.org
Subject: bug#31953: [VanL] Re: bug#31953: feature request - `highlight-rx` interactively
Date: Tue, 15 Oct 2019 09:53:16 +0200 [thread overview]
Message-ID: <87a7a2qwb7.fsf@gnus.org> (raw)
In-Reply-To: <646a4a85cca29e6ca83e1b5b2004902b@webmail.orcon.net.nz> (Phil Sainty's message of "Tue, 15 Oct 2019 15:39:43 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> I think the idea is to be able to *interactively* enter rx syntax
> and have it highlighted (as opposed to `highlight-regexp' which will
> obviously treat what you enter interactively as an actual regexp,
> rather than something to be transformed into one).
>
> i.e. These would be equivalent:
>
> M-x highlight-rx RET (or "foo" "bar") RET
> M-x highlight-regexp RET \(foo\|bar\) RET
Oh, I see.
I think it would be rather odd to have just one regexp-reading command
that uses the rx syntax interactively. If this is something we want
(and I don't really envision people willingly typing in rx forms
interactively), then it should be fixed in `read-regexp'. It could, for
instance, have a keystroke that changes the input mode.
But do we think that people want to type in rx forms?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-15 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 7:47 bug#31953: feature request - `highlight-rx` interactively Van L
2019-10-09 22:02 ` Lars Ingebrigtsen
2019-10-14 23:54 ` bug#31953: [VanL] " Lars Ingebrigtsen
2019-10-15 0:35 ` Lars Ingebrigtsen
2019-10-15 2:39 ` Phil Sainty
2019-10-15 7:53 ` Lars Ingebrigtsen [this message]
2019-10-15 8:37 ` Michael Heerdegen
2019-10-15 8:43 ` Lars Ingebrigtsen
2019-10-15 9:09 ` Michael Heerdegen
2019-10-15 14:34 ` Drew Adams
2019-11-03 22:27 ` Juri Linkov
2019-10-20 6:34 ` bug#31953: [VanL] " VanL
2019-10-20 15:49 ` Juri Linkov
2019-10-20 23:35 ` Noam Postavsky
2019-10-21 21:19 ` Juri Linkov
2019-11-02 8:30 ` VanL
2019-11-18 21:42 ` Juri Linkov
2019-11-19 12:34 ` VanL
2019-11-19 21:39 ` VanL
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=87a7a2qwb7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=31953@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
--cc=van@scratch.space \
/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).