unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: ndame <laszlomail@protonmail.com>
Cc: 53181@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#53181: Live preview of regexp replace
Date: Tue, 11 Jan 2022 11:04:16 +0200	[thread overview]
Message-ID: <868rvmiqrj.fsf@mail.linkov.net> (raw)
In-Reply-To: <qIEDWCcvKmsE-kCXYdukDgNEaBJiXpPEiINLkOHm_aqQnfI4u2Ut1-jaQVEuRjWr9F5ijmAd8f35tTxGjbwMkCUnMKiVrKsuIaB5wCuzN6w=@protonmail.com> (ndame via's message of "Tue, 11 Jan 2022 06:41:50 +0000")

> I've been using the visual regexp package for a while and it's really
> useful:
>
> https://github.com/benma/visual-regexp.el
>
> It would improve the core emacs experience if the built in regexp replace
> did this as well.  When constructing a regexp replace it's really useful to
> see the match and the capturing groups instantly in the buffer, and also
> the resulting text on the fly when typing the replacement.  It spares you
> from doing several test-fix cycles until you get the regexp replacement
> right, because you have an instant live preview of everything in the target
> buffer.
>
> Adding this feature would benefit the default regexp replace experience a lot.

This is exactly what Augusto is currently doing in bug#53126.





  reply	other threads:[~2022-01-11  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  6:41 bug#53181: Live preview of regexp replace ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11  9:04 ` Juri Linkov [this message]
2022-01-11 13:28   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 17:58     ` Juri Linkov
2022-01-11 18:27       ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13  7:23       ` Lars Ingebrigtsen

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=868rvmiqrj.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=53181@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --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).