From: Gregory Heytings <gregory@heytings.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Ergus <spacibba@aol.com>,
47599-done@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#47599: [External] : bug#47599: 28.0.50; Feature request improve/update isearch
Date: Tue, 06 Apr 2021 22:43:47 +0000 [thread overview]
Message-ID: <acf6f0cd7e4c7e701cab@heytings.org> (raw)
In-Reply-To: <SA2PR10MB44749AA695BD9A54ABB74D63F3769@SA2PR10MB4474.namprd10.prod.outlook.com>
>> While we're improving isearch, there is another minor change that I
>> think would improve its behavior, namely to go to the next/previous
>> match when changing the search direction, instead of hitting the same
>> match before moving to the next/previous one with the next C-s/C-r.
>> This change is so small that I'm not sure it's worth creating a
>> defcustom for it, but you might have a different opinion.
>
> Please do NOT do this. There are reasons we want to stay at the same
> search hit.
>
Okay, so I have the answer to my own question: this should become yet
another user option.
>
> One of them has already surfaced in these (lamentable) discussions of
> isearch "improvements":
>
Why "lamentable"???
next prev parent reply other threads:[~2021-04-06 22:43 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 [this message]
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
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=acf6f0cd7e4c7e701cab@heytings.org \
--to=gregory@heytings.org \
--cc=47599-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).