unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 48009@debbugs.gnu.org
Subject: bug#48009: 28.0.50; Support query-regexp-replace using re-builder
Date: Sun, 25 Apr 2021 10:19:04 -0500	[thread overview]
Message-ID: <CADwFkmk9AL9r2ShWYVc=CB+wVzj_wfz84FVBid0S8iELZAkemQ@mail.gmail.com> (raw)
In-Reply-To: <b1a4c710-af9a-7ab8-36dc-9348a4a1d2ae@orcon.net.nz>

Phil Sainty <psainty@orcon.net.nz> writes:

> That could be very nice, although it feels like a pretty significant
> complication.  Also, re-builder's interactive updates can sometimes
> need a manual C-c C-u (`reb-force-update') if it gets confused (which
> I think occasionally happens when the regexp is invalid?), and that
> might not be great.

True, it would need to be robust enough to handle most of what you throw
at it.  But even with some warts, it would be a significant improvement,
I think.  If it is optional, users run less risk of being caught
unawares.

A naive approach would be to run something akin to `reb-force-update'
automatically after some delay, but I have no idea if that would work in
practice.

> Or did you mean to use the isearch highlighting code, which is perhaps
> more forgiving of temporary invalid states?

I'm not familiar with the code, so I can't help with ideas for how to
best implement something like this, unfortunately.





  reply	other threads:[~2021-04-25 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  3:36 bug#48009: 28.0.50; Support query-regexp-replace using re-builder Phil Sainty
2021-04-25 10:46 ` Stefan Kangas
2021-04-25 14:51   ` Phil Sainty
2021-04-25 15:19     ` Stefan Kangas [this message]
2021-04-26 23:53 ` Tak Kunihiro
2021-05-03  3:42 ` Karthik Chikmagalur

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='CADwFkmk9AL9r2ShWYVc=CB+wVzj_wfz84FVBid0S8iELZAkemQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=48009@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    /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).