From: Gregory Heytings <gregory@heytings.org>
To: Ergus <spacibba@aol.com>
Cc: 47599-done@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#47599: 28.0.50; Feature request improve/update isearch
Date: Wed, 07 Apr 2021 11:33:53 +0000 [thread overview]
Message-ID: <3ec7e2e58a59922df0cb@heytings.org> (raw)
In-Reply-To: <20210407112050.uewsibrpxtn3p6ho@Ergus>
>> And here is an updated patch which adds three options to isearch-exit:
>> C-u RET moves point to the other end, C-u C-u RET activates region
>> around match, C-u C-u C-u RET moves point to the other end and activate
>> region around match.
>
> Hi Gregory:
>
> Maybe I am wrong but I think it makes no sense to add C-u RET for this;
> because it is not better than C-r RET. Same applies to the other two
> commands.
>
I have no strong opinion, I proposed this patch because of your request.
But C-u RET is better I think, it's a single command instead of two (C-r
RET and C-s RET). For the two other commands, I don't know an easy way to
mark the match.
>
> I am only interested in the first one really;
>
Yes, I was proposing something more general, with what I understood from
the discussion.
>
> But IMO the C-u C-u C-u is not the way we should go..
>
I think it's easy to type, much easier than M-s RET for example, but as I
sait I have no strong opinion on this, it's fine if my patch isn't
applied.
prev parent reply other threads:[~2021-04-07 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210405020725.ob7bewlin7cid4pa.ref@Ergus>
2021-04-05 2:07 ` bug#47599: 28.0.50; Feature request improve/update isearch Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 19:16 ` Juri Linkov
2021-04-06 20:38 ` Gregory Heytings
2021-04-06 21:01 ` Gregory Heytings
2021-04-06 21:32 ` Gregory Heytings
2021-04-06 22:39 ` bug#47599: [External] : " Drew Adams
2021-04-06 22:43 ` Gregory Heytings
2021-04-06 23:26 ` Gregory Heytings
2021-04-07 16:20 ` Juri Linkov
2021-04-07 17:58 ` Gregory Heytings
2021-04-08 19:05 ` Juri Linkov
2021-04-07 2:29 ` Eli Zaretskii
2021-04-07 10:44 ` Gregory Heytings
2021-04-07 11:20 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 11:33 ` Gregory Heytings [this message]
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=3ec7e2e58a59922df0cb@heytings.org \
--to=gregory@heytings.org \
--cc=47599-done@debbugs.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).