all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53181@debbugs.gnu.org
Subject: bug#53181: Live preview of regexp replace
Date: Tue, 11 Jan 2022 06:41:50 +0000	[thread overview]
Message-ID: <qIEDWCcvKmsE-kCXYdukDgNEaBJiXpPEiINLkOHm_aqQnfI4u2Ut1-jaQVEuRjWr9F5ijmAd8f35tTxGjbwMkCUnMKiVrKsuIaB5wCuzN6w=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 954 bytes --]

             reply	other threads:[~2022-01-11  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  6:41 ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-11  9:04 ` bug#53181: Live preview of regexp replace Juri Linkov
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

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

  git send-email \
    --in-reply-to='qIEDWCcvKmsE-kCXYdukDgNEaBJiXpPEiINLkOHm_aqQnfI4u2Ut1-jaQVEuRjWr9F5ijmAd8f35tTxGjbwMkCUnMKiVrKsuIaB5wCuzN6w=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53181@debbugs.gnu.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 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.