From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: contovob@tcd.ie, Ergus <spacibba@aol.com>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: RE: isearch region or thing at point.
Date: Sat, 4 May 2019 15:40:29 -0700 (PDT) [thread overview]
Message-ID: <8096bd54-4505-481c-9f8a-deeff33df2ac@default> (raw)
In-Reply-To: <87sgtuszek.fsf@mail.linkov.net>
> > (Note that we already give 2 bindings to
> > `isearch-toggle-case-fold', which we need not do.)
>
> The other is isearch-toggle-char-fold.
Oops - my bad. Eye-scanned too quickly.
> > It would be good to "standardize" bindings - say
> > reserve `M-w' (e.g. on a prefix key) for the
> > "copy-region" (or similar) action
>
> I remember you had a key to grab the region into the minibuffer.
> This is what Ergus wants.
I don't think this thread is about grabbing the region
text into the minibuffer. Ergus grabs it into Isearch
as the search string.
And I don't think I have a command that grabs the
region into the minibuffer.
What I have is a command that copies the current
search string to the kill ring. See previous posts
in this thread.
I posted the code for the command, suggesting that
we add it to vanilla Emacs and bind it (as I do) to
`M-w'. Here it is again (just rename prefix
`isearchp-' to `isearch-'):
(defun isearchp-kill-ring-save ()
"Copy the current search string to the kill ring."
(interactive)
(kill-new isearch-string)
(let ((message-log-max nil))
(message "Copied search string as kill"))
(sit-for 1)
(isearch-update))
next prev parent reply other threads:[~2019-05-04 22:40 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
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 [this message]
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=8096bd54-4505-481c-9f8a-deeff33df2ac@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).