From: Juri Linkov <juri@linkov.net>
To: Andrea Greselin <greselin.andrea@gmail.com>
Cc: 52394@debbugs.gnu.org
Subject: bug#52394: 27.2; Isearch with char folding enabled doesn’t match equivalent strings
Date: Sat, 11 Dec 2021 22:34:05 +0200 [thread overview]
Message-ID: <864k7elw3m.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAJ_oJbZ1r_zhu8iAEbiROVJUYEKw2O=DEihbRD5KbgLntcC2Sg@mail.gmail.com> (Andrea Greselin's message of "Sat, 11 Dec 2021 21:13:01 +0100")
> I guess that removing equivalent characters would help make the string
> that matches longer, right? In this case having the possibility of
> building the sets of equivalent characters from zero would help. (For
> me, just the equivalence of straight and curly quotes would cover 90%
> of the use cases.) The options for customising these sets AFAIK are
> ‘char-fold-exclude’, but it’s not for building them from null, and
> maybe the ‘char-fold-table’, but I’m not sure as to how to edit it, it
> looks like it’s more for internal use than for the user to tweak.
Right, it's possible to customize char-fold-exclude to make the string longer.
As for how to do this without customization, internally maybe it would be
possible to add regexp back references to reuse parts of the previous regexps
constructed for the same letter.
next prev parent reply other threads:[~2021-12-11 20:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 20:41 bug#52394: 27.2; Isearch with char folding enabled doesn’t match equivalent strings Andrea Greselin
2021-12-10 2:00 ` Michael Heerdegen
2021-12-10 7:51 ` Juri Linkov
2021-12-10 11:00 ` Andrea Greselin
2021-12-11 19:46 ` Juri Linkov
2021-12-11 20:13 ` Andrea Greselin
2021-12-11 20:34 ` Juri Linkov [this message]
2021-12-11 21:14 ` Andrea Greselin
2021-12-12 8:37 ` Juri Linkov
2021-12-12 9:31 ` Andrea Greselin
2021-12-12 17:19 ` Juri Linkov
2021-12-12 17:53 ` Eli Zaretskii
2021-12-12 18:06 ` Juri Linkov
2021-12-12 18:25 ` Eli Zaretskii
2021-12-12 18:30 ` Juri Linkov
2021-12-12 18:43 ` Eli Zaretskii
2021-12-12 18:54 ` Juri Linkov
2021-12-12 18:59 ` Eli Zaretskii
2021-12-12 19:12 ` 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=864k7elw3m.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52394@debbugs.gnu.org \
--cc=greselin.andrea@gmail.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).