From: Drew Adams <drew.adams@oracle.com>
To: Ergus <spacibba@aol.com>, Eli Zaretskii <eliz@gnu.org>
Cc: contovob@tcd.ie, juri@linkov.net, emacs-devel@gnu.org
Subject: RE: isearch region or thing at point.
Date: Sat, 4 May 2019 07:17:50 -0700 (PDT) [thread overview]
Message-ID: <45220b6f-8236-41fa-a520-fd7c562072da@default> (raw)
In-Reply-To: <20190504121526.mslnh3xqgc64dy7t@Ergus>
> This patch has changed a lot because some others made suggestions I
> considered useful. I will attach the new patch in another mail.
>
> On the other hand it makes sense that M-w should be used in case the
> user wants to add the text in the minibuffer to the kill-ring.
> (Something like isearchp-kill-ring-save)
>
> So maybe M-r (region) or M-i (insert) must be used for what I propose
> and Drew may add the isearch-kill-ring-save function he wrote and bind
> it to M-w. That way there will be all the copy functionalities in place.
I would prefer that, yes. `M-w' to copy to the
kill-ring (as usual).
Do you need an actual patch to include the command
I sent, or can you please just include it (renaming
prefix `isearchp-' to `isearch-')?
> But then we must recommend bind M-r or M-i (or whatever) for similar
> functionalities. And if possible correct other modes to be consistent
> with that (if that does not start a religious war here please).
Sorry, I don't know what you mean, there. `M-r' is
(and has long been) `isearch-toggle-regexp'.
> I will try to do the same for replace-like commands.
(Not sure what you mean by that, either.)
next prev parent reply other threads:[~2019-05-04 14:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 0:14 isearch region or thing at point Ergus
2019-04-27 2:15 ` Basil L. Contovounesios
2019-04-29 0:41 ` Ergus
2019-04-29 1:30 ` Ergus
2019-04-29 1:31 ` Ergus
2019-04-29 19:41 ` Juri Linkov
2019-04-29 20:50 ` Ergus
2019-04-30 15:39 ` Drew Adams
2019-04-30 16:57 ` Ergus
2019-04-30 19:58 ` Juri Linkov
2019-04-30 16:25 ` Ergus
2019-04-30 18:49 ` Noam Postavsky
2019-04-30 19:03 ` Ergus
2019-04-30 19:24 ` Noam Postavsky
2019-04-30 20:05 ` Ergus
2019-04-30 20:38 ` Noam Postavsky
2019-04-30 22:39 ` Basil L. Contovounesios
2019-04-30 23:16 ` Ergus
2019-04-30 23:33 ` Basil L. Contovounesios
2019-05-01 0:13 ` Ergus
2019-05-01 20:57 ` Juri Linkov
2019-05-03 16:27 ` Basil L. Contovounesios
2019-05-01 11:20 ` Ergus
2019-05-01 14:33 ` Drew Adams
2019-05-01 16:03 ` Ergus
2019-05-01 16:25 ` Drew Adams
2019-05-03 16:28 ` Basil L. Contovounesios
2019-05-04 9:29 ` Eli Zaretskii
2019-05-03 16:28 ` Basil L. Contovounesios
2019-05-04 9:26 ` Eli Zaretskii
2019-05-04 12:15 ` Ergus
2019-05-04 14:17 ` Drew Adams [this message]
2019-05-04 14:56 ` Ergus
2019-05-04 15:24 ` Drew Adams
2019-05-04 21:06 ` Juri Linkov
2019-05-04 22:40 ` Drew Adams
2019-05-06 19:41 ` Juri Linkov
2019-05-07 2:56 ` Drew Adams
2019-05-07 19:56 ` Ergus
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=45220b6f-8236-41fa-a520-fd7c562072da@default \
--to=drew.adams@oracle.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=spacibba@aol.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).