unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73723@debbugs.gnu.org
Subject: bug#73723: 31.0.50; Add copy/kill/mark commands to isearch
Date: Fri, 11 Oct 2024 01:10:28 +1300	[thread overview]
Message-ID: <d5094399f009481f0ba87b47ed62894c@webmail.orcon.net.nz> (raw)
In-Reply-To: <86r08o36np.fsf@gnu.org>

On 2024-10-10 17:48, Eli Zaretskii wrote:
>> Date: Thu, 10 Oct 2024 09:33:41 +1300
>> From: Phil Sainty <psainty@orcon.net.nz>
>>   (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)
> 
> Sounds useful, but "M-x M-w" is already taken, unfortunately.

"M-s M-w" does have a binding to `eww-search-words' in the global 
keymap,
but I'm not sure that needs to prevent us using it here?

Certainly `eww-search-words' doesn't react to the current isearch match,
so I think there's not currently a particular reason why one would 
invoke
the global binding whilst isearching.  (You *could* set the mark and 
then
search to extend the region before calling `eww-search-words' for that
region; but you could trivially still do that simply by exiting the
isearch explicitly.)


> For isearch-kill-match, should there also be a command to kill _all_
> the matches?

Potentially, although there's a library iedit.el which provides that
kind of functionality.  It has an `iedit-mode-from-isearch' command
to invoke iedit on the matched text.  (Although to specifically kill
all matches, it looks like you'd need to follow that command by
restarting the isearch and *then* call `isearch-kill-match'.


-Phil






  reply	other threads:[~2024-10-10 12:10 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 [this message]
2024-10-10  6:37 ` Juri Linkov
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=d5094399f009481f0ba87b47ed62894c@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=73723@debbugs.gnu.org \
    --cc=eliz@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).