From: Juri Linkov <juri@linkov.net>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 73723@debbugs.gnu.org
Subject: bug#73723: 31.0.50; Add copy/kill/mark commands to isearch
Date: Thu, 10 Oct 2024 09:37:37 +0300 [thread overview]
Message-ID: <86a5fc5uq6.fsf@mail.linkov.net> (raw)
In-Reply-To: <194a0202fd0c9b752d2f6e4f3ff642d8@webmail.orcon.net.nz> (Phil Sainty's message of "Thu, 10 Oct 2024 09:33:41 +1300")
> I find the following useful, and sometimes see others asking for
> the same thing. Shall we add these to Emacs?
>
> (defun isearch-copy-match ()
> "Copy the currently-matched text to the kill ring."
> (interactive)
> (kill-new (buffer-substring (min (point) isearch-other-end)
> (max (point) isearch-other-end))))
>
> (defun isearch-kill-match ()
> "Kill the currently-matched text."
> (interactive)
> (kill-region (min (point) isearch-other-end)
> (max (point) isearch-other-end)))
>
> (defun isearch-mark-match ()
> "Exit isearch, marking the last match."
> (interactive)
> (set-mark isearch-other-end)
> (isearch-exit)
> (activate-mark))
>
> (define-key isearch-mode-map (kbd "M-s M-w") #'isearch-copy-match)
> (define-key isearch-mode-map (kbd "M-s C-w") #'isearch-kill-match)
> (define-key isearch-mode-map (kbd "M-s C-SPC") #'isearch-mark-match)
> (define-key isearch-mode-map (kbd "M-s C-@") #'isearch-mark-match)
I have a patch that I'm using for a long time every day.
It allows exiting Isearch with 'S-RET' that activates
the region on the current match. This allows using
the standard keys afterwards: 'M-w' to copy the match,
'C-w' to kill the match, etc. Does this eliminate the need
to add more Isearch commands?
next prev parent reply other threads:[~2024-10-10 6:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 20:33 bug#73723: 31.0.50; Add copy/kill/mark commands to isearch Phil Sainty
2024-10-09 23:47 ` Stefan Kangas
2024-10-10 4:48 ` Eli Zaretskii
2024-10-10 12:10 ` Phil Sainty
2024-10-10 6:37 ` Juri Linkov [this message]
2024-10-10 7:38 ` Eli Zaretskii
2024-10-10 17:32 ` Juri Linkov
2024-10-10 16:58 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 17:35 ` Juri Linkov
2024-10-10 18:20 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 18:31 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 18:41 ` Juri Linkov
2024-10-10 18:54 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 18:40 ` Juri Linkov
2024-10-10 22:04 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86a5fc5uq6.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=73723@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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).