unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@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: Sat, 25 Dec 2021 00:14:48 -0500	[thread overview]
Message-ID: <E1n0zOK-0002Lk-0S@fencepost.gnu.org> (raw)
In-Reply-To: <Negv3wOcFYBe421Od7WcjI2qb_8OmxuOfST5KD_4qLa31_lmvVntUaO53yPsFYnwZrdGFB2-6uzEjR9w4Fg5SJ2Xq62itH70CpplFIwOKvA=@protonmail.com> (bug-gnu-emacs@gnu.org)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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?

That is an interesting idea, but I think it would be a pain unless
there is a convenient, easy way to move between those two parts of the
minibuffer.

Any ideas for how to do that?

One idea that occurs to me is to define two special movement commands
and bind M-{ and M-} to them.  It is unusual for the FROM and TO
strings to contain multiple paragraphs, so the standard bindings of
those two keys won't be much missed.


-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  parent reply	other threads:[~2021-12-25  5:14 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 [this message]
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=E1n0zOK-0002Lk-0S@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).