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: 52751@debbugs.gnu.org
Subject: bug#52751: 27.1; Go back to editing the from part in query replace
Date: Thu, 23 Dec 2021 19:18:23 +0200	[thread overview]
Message-ID: <8635mjcpts.fsf@mail.linkov.net> (raw)
In-Reply-To: <Negv3wOcFYBe421Od7WcjI2qb_8OmxuOfST5KD_4qLa31_lmvVntUaO53yPsFYnwZrdGFB2-6uzEjR9w4Fg5SJ2Xq62itH70CpplFIwOKvA=@protonmail.com> (ndame via's message of "Thu, 23 Dec 2021 06:55:01 +0000")

> 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, or I can submit some dummy TO value, cancel the replace, restart
> it  and then use history to fix the FROM value.
>
> There should be an easy way to go back to editing FROM without cumbersome
> workarounds.
>
> Mainstream UIs solve this by having different input fields where I can
> switch to and edit any input field before submitting. Maybe the FROM -> TO
> input should be the default with a preinserted -> arrow, so the user can
> switch back an forth easily between FROM and TO?

Preinserting an arrow by default would be confusing for users.
But maybe M-n could insert it.





  reply	other threads:[~2021-12-23 17:18 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 [this message]
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
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=8635mjcpts.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=52751@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 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).