From: Juri Linkov <juri@jurta.org>
To: emacs-devel@gnu.org
Subject: Re: History for query replace pairs
Date: Sun, 05 Oct 2014 02:36:57 +0300 [thread overview]
Message-ID: <87mw9b8l0m.fsf@mail.jurta.org> (raw)
In-Reply-To: <87lhovik5c.fsf@lifelogs.com> (Ted Zlatanov's message of "Sat, 04 Oct 2014 17:45:35 -0400")
> T> I created a quick proof of concept implementation. It changes the behavior
> T> of the arrow keys for the query-replace(-regexp) FROM prompt. You can stll
> T> access the original behavior with M-p/n.
>
> T> So when you start a query-replace and press the up arrow then
> T> search/replace history is rendered as FROM -> TO pairs. The -> marker is
> T> highlighted and intangible, the cursor jumps over it and you are free to
> T> edit the search/replace string. If you submit a FROM->TO pair from the FROM
> T> input field with RET then the replacement is started immediately. If you
> T> submit a simple string (without the marker) then it behaves as usual and
> T> asks for a TO string.
>
> I'd like to make this part of the Emacs core, disabled by default. Any
> objections? I think it's nicer-looking than the current UI.
>
> If not, maybe Tom would like to make it a GNU ELPA package?
I realized right now that the most intuitive and convenient way is
to implement a new general function to read two values in the minibuffer
with two entry fields. These fields could be like in Widget/Customization UI
where the user can switch the entry point between two fields.
Anything between them would be read-only like the current prompt is, e.g.
Query replace: [from] with: [to]
where [from] and [to] are entry fields. `M-p' will update these two fields
with the previous values from the history.
next prev parent reply other threads:[~2014-10-04 23:36 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 20:20 History for query replace pairs Tom
2014-08-08 20:28 ` Drew Adams
2014-08-08 23:38 ` Juri Linkov
2014-08-09 5:35 ` Herring, Davis
2014-08-10 1:18 ` Josh
2014-08-10 5:59 ` Tom
2014-08-11 18:34 ` Tom
2014-10-04 21:45 ` Ted Zlatanov
2014-10-04 23:36 ` Juri Linkov [this message]
2014-10-05 1:52 ` Yuri Khan
2014-10-05 21:54 ` Juri Linkov
2014-10-05 7:09 ` Andreas Schwab
2014-10-05 1:52 ` Stefan Monnier
2014-10-05 5:59 ` Tom
2014-10-06 0:46 ` Ted Zlatanov
2014-10-06 20:17 ` Tom
2014-10-06 22:35 ` Juri Linkov
2014-10-07 22:11 ` Juri Linkov
2014-10-14 17:14 ` Stefan Monnier
2014-10-14 19:02 ` Juri Linkov
2014-10-14 19:13 ` Alan Mackenzie
2014-10-14 19:44 ` Juri Linkov
2014-10-14 20:15 ` Alan Mackenzie
2014-10-14 20:16 ` Drew Adams
2014-10-14 20:28 ` Juri Linkov
2014-10-14 21:19 ` Drew Adams
2014-10-14 20:05 ` Andreas Schwab
2014-10-14 20:09 ` Alan Mackenzie
2014-10-14 20:23 ` Andreas Schwab
2014-10-21 18:23 ` Stefan Monnier
2014-10-21 22:53 ` Juri Linkov
2014-10-22 12:58 ` Stefan Monnier
2014-10-23 9:06 ` Artur Malabarba
2014-10-25 20:57 ` Juri Linkov
2014-10-26 1:12 ` Artur Malabarba
2014-10-26 2:31 ` Stefan Monnier
2014-10-26 6:58 ` Andreas Schwab
2014-10-25 20:52 ` Juri Linkov
2014-10-26 2:29 ` Stefan Monnier
2014-10-26 23:27 ` Juri Linkov
2014-11-03 13:30 ` Ted Zlatanov
2014-11-03 23:46 ` Juri Linkov
2014-11-04 0:59 ` Ted Zlatanov
2014-11-04 23:09 ` Juri Linkov
2014-11-05 1:55 ` Stefan Monnier
2014-11-05 23:20 ` Juri Linkov
2014-11-06 2:35 ` Stefan Monnier
2014-11-07 23:34 ` Juri Linkov
2014-11-08 0:59 ` Ted Zlatanov
2014-11-08 8:46 ` Eli Zaretskii
2014-11-08 10:29 ` Juri Linkov
2014-11-08 11:24 ` Eli Zaretskii
2014-11-08 15:28 ` Stefan Monnier
2014-11-08 17:29 ` Eli Zaretskii
2014-11-08 22:52 ` Juri Linkov
2014-11-09 2:01 ` Stefan Monnier
2014-11-09 16:15 ` Eli Zaretskii
2014-11-09 17:11 ` Juri Linkov
2014-11-09 22:14 ` Stefan Monnier
2014-11-09 23:12 ` Juri Linkov
2014-11-09 22:10 ` Stefan Monnier
2014-11-09 2:29 ` Paul Eggert
2014-11-09 17:15 ` Juri Linkov
2014-11-08 22:51 ` Juri Linkov
2014-11-09 17:29 ` Eli Zaretskii
2014-11-08 10:15 ` Juri Linkov
2014-11-08 8:25 ` Eli Zaretskii
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=87mw9b8l0m.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
/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).