From: Eli Zaretskii <eliz@gnu.org>
To: bruce.connor.am@gmail.com
Cc: 22090@debbugs.gnu.org, acm@muc.de
Subject: bug#22090: Isearch is sluggish and eventually refuses further service with "[Too many words]".
Date: Sat, 05 Dec 2015 20:34:33 +0200 [thread overview]
Message-ID: <831tb0g2x2.fsf@gnu.org> (raw)
In-Reply-To: <CAAdUY-Kfu7rmwR3B0X948feA8ASCA9bU2oZFo8XGYmRfmT4qaw@mail.gmail.com>
> Date: Sat, 5 Dec 2015 18:12:52 +0000
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: Alan Mackenzie <acm@muc.de>, 22090@debbugs.gnu.org
>
> 2015-12-05 17:32 GMT+00:00 Eli Zaretskii <eliz@gnu.org>:
> >> Because there are some characters in each regexp that don't have
> >> lower/upper-case equivalents. For instance, if I use the
> >> "\\(\\(a[´`]?\\|[áà𝑎]\\)" regexp, that's enough to match A or À, but
> >> it's not enough to match a variety of other chars (𝔸𝕬𝖠𝗔𝘈𝘼𝙰🄰).
> >
> > You don't need to match the latter set. Character folding is applied
> > _after_ case folding, not before. So characters that don't have a
> > lower-case variant simply shouldn't match a lower-case a -- and they
> > won't, if you just let case-insensitive regexp matching do its job.
>
> Given that char-folding is a new feature, how it combines with
> case-folding is entirely up to us, and I have really no idea what
> would be TRT.
I don't think there's any reasonable alternative, because for
characters that have a decomposition, you wouldn't downcase the result
of the decomposition, would you?
The Unicode Standard also says this much (p.158):
In principle, normalization needs to be done after case folding,
because case folding does not preserve the normalized form of
strings in all instances.
(There are a couple of examples there showing why the reverse order
could cause incorrect results.)
So if this is true for normalization, it should also be true for the
case in point.
> However, if that is your opinion, I'm more than happy to accept that
> the current situation ('a' doesn't match '𝔸𝕬𝖠𝗔𝘈𝘼𝙰🄰') is TRT,
> given that it has the simplest implementation. :-)
Yes, I think it's TRT.
next prev parent reply other threads:[~2015-12-05 18:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 4:20 bug#22090: Isearch is sluggish and eventually refuses further service with "[Too many words]" Alan Mackenzie
2015-12-04 9:23 ` Eli Zaretskii
2015-12-04 15:16 ` Artur Malabarba
2015-12-04 15:23 ` Eli Zaretskii
2015-12-04 16:06 ` Artur Malabarba
2015-12-04 16:27 ` Eli Zaretskii
2015-12-04 16:37 ` Artur Malabarba
2015-12-04 18:48 ` Eli Zaretskii
2015-12-04 19:59 ` Artur Malabarba
2015-12-05 9:19 ` Eli Zaretskii
2015-12-04 15:49 ` Random832
2015-12-04 16:21 ` Artur Malabarba
2015-12-04 16:37 ` Random832
2015-12-04 16:51 ` Artur Malabarba
2015-12-04 18:24 ` Eli Zaretskii
[not found] ` <mailman.1363.1449242229.31583.bug-gnu-emacs@gnu.org>
2015-12-04 17:01 ` Alan Mackenzie
2015-12-04 19:21 ` Alan Mackenzie
2015-12-04 20:08 ` Eli Zaretskii
2015-12-04 20:49 ` Artur Malabarba
2015-12-04 23:00 ` Alan Mackenzie
2015-12-05 17:23 ` Artur Malabarba
2015-12-05 17:32 ` Eli Zaretskii
2015-12-05 18:12 ` Artur Malabarba
2015-12-05 18:34 ` Eli Zaretskii [this message]
2015-12-05 18:52 ` Alan Mackenzie
2015-12-06 12:50 ` Artur Malabarba
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831tb0g2x2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22090@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=bruce.connor.am@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.