From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@jurta.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"14729@debbugs.gnu.org" <14729@debbugs.gnu.org>,
Dani Moncayo <dmoncayo@gmail.com>
Subject: bug#14729: [External] : bug#14729: 24.3.50; Isearch oddity
Date: Mon, 6 Dec 2021 16:01:16 +0000 [thread overview]
Message-ID: <SJ0PR10MB54881A057B6975EDA1A73FDDF36D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <865ys2yt5z.fsf@mail.linkov.net>
> >> > Honestly, I have no idea what is right and what
> >> > is wrong in this situation
> >>
> >> Me neither, but it's not quite optimal the way it is now.
> >
> > That exchange is telling.
> >
> > As I suggested, let users control the behavior
> > (Isearch+ does that). Don't look for a single
> > behavior that's "right" for everyone in all
> > contexts.
>
> This means adding a new user option for this small detail?
I described what I do in Isearch+. There's a
user option, AND users can choose/change the
current behavior on the fly, during Isearch.
There are of course other ways to skin this cat.
My point above was that you seem to have come to
the (correct) conclusion that one size doesn't
fit all. How you want to go forward from that
conclusion is TBD.
next prev parent reply other threads:[~2021-12-06 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 9:58 bug#14729: 24.3.50; Isearch oddity Dani Moncayo
2013-06-27 23:44 ` Juri Linkov
2013-06-29 17:22 ` Dani Moncayo
2013-06-29 21:53 ` Juri Linkov
2013-06-29 22:34 ` Dani Moncayo
2013-06-30 3:11 ` Drew Adams
2021-12-04 3:51 ` Lars Ingebrigtsen
2021-12-04 16:48 ` bug#14729: [External] : " Drew Adams
2021-12-04 19:59 ` Juri Linkov
2021-12-04 22:06 ` Lars Ingebrigtsen
2021-12-05 9:35 ` Juri Linkov
2021-12-05 20:22 ` Lars Ingebrigtsen
2021-12-06 2:09 ` bug#14729: [External] : " Drew Adams
2021-12-06 9:33 ` Juri Linkov
2021-12-06 9:40 ` Lars Ingebrigtsen
2021-12-06 16:01 ` Drew Adams [this message]
2021-12-06 17:03 ` Juri Linkov
2021-12-07 20:48 ` Lars Ingebrigtsen
2021-12-07 21:53 ` Juri Linkov
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=SJ0PR10MB54881A057B6975EDA1A73FDDF36D9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=14729@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=juri@jurta.org \
--cc=larsi@gnus.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).