From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22090@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>
Subject: bug#22090: Isearch is sluggish and eventually refuses further service with "[Too many words]".
Date: Fri, 4 Dec 2015 16:37:08 +0000 [thread overview]
Message-ID: <CAAdUY-K4Up1X4Un+60X2R0PyKykxCNXY__2sjcN3sD72daSxgA@mail.gmail.com> (raw)
In-Reply-To: <83bna6govv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On 4 Dec 2015 4:27 pm, "Eli Zaretskii" <eliz@gnu.org> wrote:
>
> > Date: Fri, 4 Dec 2015 16:06:40 +0000
> > From: Artur Malabarba <bruce.connor.am@gmail.com>
> > Cc: Alan Mackenzie <acm@muc.de>, 22090@debbugs.gnu.org
> >
> > > Thanks. Is there any reasonably simple way of describing the
> > > resulting limitations (i.e. what will NOT match) on the user manual
> > > level?
> >
> > Basically, 'a' will match similar characters (like '𝑎' and 'á') and
> > their upper-case equivalents (like 'Á'). 'a' will NOT match characters
> > similar to 'A' that don't have a lower-case equivalent (like '𝔸') in
> > the unicode standard.
>
> What about ligatures, or symbols like ℻?
Won't match cross-case.
> Also, by "lower-case equivalent" do you mean a case mapping defined by
> the UCD
Yes. Visual appearance is irrelevant.
Strictly speaking, to match a general character, you need to search for its
decomposition. If this character also has a case "equivalent" (as per
current-case-table), you can also search for the decomposition of this
equivalent.
[-- Attachment #2: Type: text/html, Size: 1599 bytes --]
next prev parent reply other threads:[~2015-12-04 16:37 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 [this message]
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
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=CAAdUY-K4Up1X4Un+60X2R0PyKykxCNXY__2sjcN3sD72daSxgA@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=22090@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.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 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.