From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, Juri Linkov <juri@linkov.net>
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 18:31:27 +0000 [thread overview]
Message-ID: <DS7PR10MB52328ED87B179836E7658FD2F3782@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <DS7PR10MB52327ED8230372CEB9CA1EEBF3782@DS7PR10MB5232.namprd10.prod.outlook.com>
Sorry, I misspoke. I was thinking that my `M-w'
copies the current search _match_, but it copies
the search string (input pattern), `isearch-string'.
The argument that it's better to use `M-w' during
search for that because you can use it multiple
times still holds, but only because you can change
the search pattern (during search) - not _also_
because the same pattern can match different text.
It probably makes sense to also have a command
that copies the current search match. And maybe
that's the best candidate for `M-w' (not a command
that copies `isearch-string').
next prev parent reply other threads:[~2024-10-10 18:31 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 [this message]
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=DS7PR10MB52328ED87B179836E7658FD2F3782@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=bug-gnu-emacs@gnu.org \
--cc=73723@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
--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).