unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	"73723@debbugs.gnu.org" <73723@debbugs.gnu.org>
Subject: bug#73723: 31.0.50; Add copy/kill/mark commands to isearch
Date: Thu, 10 Oct 2024 21:40:15 +0300	[thread overview]
Message-ID: <864j5jyf74.fsf@mail.linkov.net> (raw)
In-Reply-To: <DS7PR10MB52327ED8230372CEB9CA1EEBF3782@DS7PR10MB5232.namprd10.prod.outlook.com> (Drew Adams's message of "Thu, 10 Oct 2024 18:20:15 +0000")

>> > FWIW, in isearch+.el I define `isearchp-kill-ring-save'
>> > and bind it to `M-w'.
>> > This has been the case since 2013.
>> 
>> Since `M-w' can't be used according to the comments in
>> https://urldefense.com/v3/__https://old.reddit.com/r/emacs/comments/1fzv
>> wig/copy_search_string_to_killring/__;!!ACWV5N9M2RV99hQ!L5HGxhm07QP4heBq
>> z0oZG6Hs1DF2e5hty8aAHJG_sxr39y7pRCFJPoP2E_m9P8iyv-lGni4NgqrGZg$
>
> I don't see anything there that says why `M-w' can't
> be used.  What's the reason you think is given there?
> Is it this?
>
>   "I have muscle memory for pressing M-w to end the
>    search and save the region from where point was
>    before starting isearch to the location where the
>    search string was found."
>
> ?

Yes, I meant exactly this feedback.

> There are other ways to get the region to be from the
> initial position to the end (if forward) or the start
> (if backward) of the search match.

Like 'C-x C-x' etc.  But 'C-x C-x' can't activate the region
on the last match.  Therefore we need another key binding.





  parent reply	other threads:[~2024-10-10 18:40 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
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 [this message]
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=864j5jyf74.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=73723@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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).