From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "24510@debbugs.gnu.org" <24510@debbugs.gnu.org>
Subject: bug#24510: 25.1; Info: searching for ` does not find what looks like `
Date: Tue, 3 May 2022 19:23:42 +0000 [thread overview]
Message-ID: <SJ0PR10MB54886C7BE34C83E8057FAC7FF3C09@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86leviilvy.fsf@mail.linkov.net>
> >> I thought that by default Isearch always should be literal,
> >> so the user could search only for plain ', and not to match
> >> its fancy variants.
> >
> > No, I want the default Isearch to fold `' with the fancy variants in
> > these modes. :-)
>
> So the users will have no way to search for ' literally?
No; see my other msgs in the thread about this.
Users _absolutely_ need the ability to search
for ` and ', as well as to search for ` and left
curly, and ' and right curly.
This is the problem. We need to give them ways
to do everything, easily, and we need to provide
reasonable default behavior. I agreed with you
that by default Isearch in Info and Help should
_not_ fold such confusables. But users need to
know that they can easily do that (e.g. a key).
And we should I think come up with reasonable
ways to help with some feedback when Emacs can
guess that maybe the user meant to get folded
behavior but didn't, e.g., looked for ` and
didn't find any occurrences. Such feedback
from guessing needs to be optional - it must
not be in-your-face and annoy.
> Or maybe better to add a new Isearch mode that char-folds only `'
I suggested having an Isearch _key_ (a toggle),
not a mode, for just that, as opposed to the
more drastic full char-folding. And I suggested
having an option to configure the confusables
to fold.
> and enable it only in Help buffers?
No, I think that any such behavior should be
configurable, e.g. by an option that lists the
modes or buffer-name regexps, to define where
to apply it.
___
There are lots of possibilities for trying
to deal with all of this, and I don't have a
perfect solution (there isn't any, I
suspect). It's worth brainstorming etc.
___
Even if we didn't have the catastrophe of the
imposition everywhere of curly quotes, we'd
have this problem (only __much__ less so) of
optionally folding confusables. It merits
some reflection and discussion - better on
emacs-devel than here, I think.
next prev parent reply other threads:[~2022-05-03 19:23 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 17:04 bug#24510: 25.1; Info: searching for ` does not find what looks like ` Drew Adams
2016-09-22 18:40 ` Eli Zaretskii
2016-09-22 19:58 ` Drew Adams
2016-09-22 20:41 ` Clément Pit--Claudel
2016-09-22 21:16 ` Drew Adams
2016-09-23 6:54 ` Eli Zaretskii
2016-09-22 20:02 ` Clément Pit--Claudel
2016-09-22 22:10 ` Noam Postavsky
2016-09-22 22:27 ` Drew Adams
2022-04-28 10:48 ` Lars Ingebrigtsen
2022-04-28 16:12 ` Drew Adams
2022-04-28 17:38 ` Juri Linkov
2022-04-28 18:15 ` Lars Ingebrigtsen
2022-04-28 19:00 ` Drew Adams
2022-04-29 6:51 ` Juri Linkov
2022-04-29 10:08 ` Lars Ingebrigtsen
2022-04-29 15:06 ` Drew Adams
2022-04-29 17:17 ` Juri Linkov
2022-04-30 11:45 ` Lars Ingebrigtsen
2022-05-01 17:11 ` Juri Linkov
2022-05-01 18:58 ` Lars Ingebrigtsen
2022-05-02 16:12 ` Juri Linkov
2022-05-03 10:33 ` Lars Ingebrigtsen
2022-05-03 14:58 ` Drew Adams
2022-05-03 17:29 ` Juri Linkov
2022-05-03 18:05 ` Lars Ingebrigtsen
2022-05-03 19:26 ` Drew Adams
2022-05-05 16:20 ` Juri Linkov
2022-05-05 16:44 ` Drew Adams
2022-05-06 23:20 ` Richard Stallman
2022-05-06 11:30 ` Lars Ingebrigtsen
2022-05-06 14:40 ` Drew Adams
2022-05-06 15:32 ` Juri Linkov
2022-05-06 17:57 ` Lars Ingebrigtsen
2022-05-03 19:23 ` Drew Adams [this message]
2022-04-29 15:01 ` Drew Adams
2022-04-28 18:58 ` Drew Adams
[not found] <<6905ca6f-0573-4a2b-b346-d5df47862e09@default>
[not found] ` <<83intneq2g.fsf@gnu.org>
[not found] ` <<7f9c8f95-a04d-4e94-9c17-8a348bf89215@default>
[not found] ` <<83d1jvds1t.fsf@gnu.org>
2016-09-23 16:02 ` Drew Adams
2016-09-23 17:48 ` Eli Zaretskii
2016-09-23 20:07 ` Clément Pit--Claudel
2016-09-24 7:28 ` Eli Zaretskii
2016-09-24 16:30 ` Clément Pit--Claudel
2016-09-24 17:08 ` Eli Zaretskii
2016-09-24 17:24 ` Clément Pit--Claudel
2016-09-24 17:57 ` Eli Zaretskii
2016-09-24 18:14 ` Clément Pit--Claudel
2016-09-24 18:34 ` Eli Zaretskii
2016-09-24 18:40 ` Clément Pit--Claudel
2016-09-24 19:16 ` Eli Zaretskii
2016-09-24 18:14 ` Drew Adams
[not found] <<<6905ca6f-0573-4a2b-b346-d5df47862e09@default>
[not found] ` <<<83intneq2g.fsf@gnu.org>
[not found] ` <<<7f9c8f95-a04d-4e94-9c17-8a348bf89215@default>
[not found] ` <<<83d1jvds1t.fsf@gnu.org>
[not found] ` <<c5f5356e-222a-48b0-9b80-dd242f982cec@default>
[not found] ` <<83mviycxse.fsf@gnu.org>
2016-09-23 21:47 ` Drew Adams
2016-09-24 7:31 ` Eli Zaretskii
2016-09-25 8:07 ` Byung-Hee HWANG (황병희, 黃炳熙)
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=SJ0PR10MB54886C7BE34C83E8057FAC7FF3C09@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=24510@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).