unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: ndame <laszlomail@protonmail.com>
Cc: 52751@debbugs.gnu.org
Subject: bug#52751: 27.1; Go back to editing the from part in query replace
Date: Sun, 26 Dec 2021 01:08:36 +0100	[thread overview]
Message-ID: <m17dbsb52z.fsf@yahoo.es> (raw)
In-Reply-To: <Negv3wOcFYBe421Od7WcjI2qb_8OmxuOfST5KD_4qLa31_lmvVntUaO53yPsFYnwZrdGFB2-6uzEjR9w4Fg5SJ2Xq62itH70CpplFIwOKvA=@protonmail.com> (ndame's message of "Thu, 23 Dec 2021 06:55:01 +0000")

ndame <laszlomail@protonmail.com> writes:

> I often run into the situation of doing a complicated query
> replace/regexp, submitting the FROM part and then during editing the
> TO part I notice an error in FROM. But I cannot go back there to fix
> it, I can either cancel the replace which deletes the FROM part,
> because it did not yet go into history [...]

The FROM value is stored in history even if you abort the query and
replace without completing it:

emacs -Q
M-% foo RET
C-g
M-% M-p (this should recover "foo").

There's room for improvement, though.  If there are complete query
replace items of the form FROM -> TO, then they are placed before the
FROM entries in the history.  Perhaps there should be a mechanism to
recover those FROM entries from history more quickly.





  parent reply	other threads:[~2021-12-26  0:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  6:55 bug#52751: 27.1; Go back to editing the from part in query replace ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-23 17:18 ` Juri Linkov
2021-12-24  4:59   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-24  5:01     ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-25  5:14 ` Richard Stallman
2021-12-25  5:23   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-25 19:18     ` Juri Linkov
2021-12-25 20:23       ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-25 20:44         ` Juri Linkov
2021-12-25 21:04           ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-26  7:45             ` Juri Linkov
2021-12-26 18:51               ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27  4:14         ` Richard Stallman
2021-12-26  0:08 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-12-26  7:49   ` Juri Linkov

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=m17dbsb52z.fsf@yahoo.es \
    --to=bug-gnu-emacs@gnu.org \
    --cc=52751@debbugs.gnu.org \
    --cc=laszlomail@protonmail.com \
    --cc=mardani29@yahoo.es \
    /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).