From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ndame <laszlomail@protonmail.com>, 50766@debbugs.gnu.org
Subject: bug#50766: Regexp paren pairs in query-replace-regexp prompt should be highlighted
Date: Mon, 4 Oct 2021 10:26:32 +0200 [thread overview]
Message-ID: <2a200c3a-1901-fda5-2423-b04eab035347@gmx.at> (raw)
In-Reply-To: <87k0ivvlyz.fsf@gnus.org>
>> With 'blink-matching-paren' on do C-M-% and type [)]. People who use
>> 'blink-matching-paren' do not type complex regexps.
>
> We do indeed -- we just live with the bogus warnings from Emacs.
So a fix for both has to hook into post-self-insert and after-change.
Which means I have to prime these before-change to avoid parsing the
buffer twice. Darn it!
martin
next prev parent reply other threads:[~2021-10-04 8:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:59 bug#50766: Regexp paren pairs in query-replace-regexp prompt should be highlighted ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-23 21:15 ` Lars Ingebrigtsen
2021-09-24 8:27 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-25 0:54 ` Lars Ingebrigtsen
2021-09-27 13:16 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-28 5:25 ` Lars Ingebrigtsen
2021-09-30 16:18 ` martin rudalics
2021-10-01 7:19 ` Lars Ingebrigtsen
2021-10-01 14:28 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-01 15:00 ` martin rudalics
2021-10-01 15:00 ` martin rudalics
2021-10-02 9:01 ` Lars Ingebrigtsen
2021-10-04 8:26 ` martin rudalics [this message]
2021-10-07 9:07 ` martin rudalics
2022-08-26 12:50 ` Lars Ingebrigtsen
2022-09-10 6:14 ` Lars Ingebrigtsen
2023-09-03 8:37 ` Stefan Kangas
2023-09-04 7:45 ` martin rudalics
2023-09-05 22:52 ` Stefan Kangas
2023-09-06 8:09 ` martin rudalics
2023-09-07 8:57 ` Eli Zaretskii
2023-09-07 9:29 ` Stefan Kangas
2023-09-07 18:12 ` martin rudalics
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=2a200c3a-1901-fda5-2423-b04eab035347@gmx.at \
--to=rudalics@gmx.at \
--cc=50766@debbugs.gnu.org \
--cc=larsi@gnus.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).