all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Lars Ingebrigtsen <larsi@gnus.org>
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 15:39:43 +1300	[thread overview]
Message-ID: <646a4a85cca29e6ca83e1b5b2004902b@webmail.orcon.net.nz> (raw)
In-Reply-To: <87o8yirgk4.fsf@gnus.org>

On 2019-10-15 13:35, Lars Ingebrigtsen wrote:
>> I was wanting to migrate from regexp to rx syntax for highlighting.
> 
> `rx' returns a normal regexp, so you can use whatever you want, can't
> you?

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







  reply	other threads:[~2019-10-15  2:39 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 [this message]
2019-10-15  7:53       ` Lars Ingebrigtsen
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=646a4a85cca29e6ca83e1b5b2004902b@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=31953@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.