GNU bug report logs - #22090
Isearch is sluggish and eventually refuses further service with "[Too many words]".

Previous Next

Package: emacs;

Reported by: Alan Mackenzie <acm <at> muc.de>

Date: Fri, 4 Dec 2015 04:26:01 UTC

Severity: normal

Done: Alan Mackenzie <acm <at> muc.de>

Bug is archived. No further changes may be made.

Full log

Message #70 received at 22090 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: bruce.connor.am <at> gmail.com
Cc: 22090 <at> debbugs.gnu.org, acm <at> muc.de
Subject: Re: bug#22090: Isearch is sluggish and eventually refuses further
 service	with "[Too many words]".
Date: Sat, 05 Dec 2015 19:32:17 +0200

> Date: Sat, 5 Dec 2015 17:23:53 +0000
> From: Artur Malabarba <bruce.connor.am <at> gmail.com>
> Cc: 22090 <at> debbugs.gnu.org
> 
> nn2015-12-04 23:00 GMT+00:00 Alan Mackenzie <acm <at> muc.de>:
> >> When case-fold-search is on the previous code would simply join these
> >> regexps with "\\(\\(a[Β΄`]?\\|[Γ‘Γ π‘Ž]\\)\\|\\(A[`Β΄]?\\|[ÁÀ]\\)\\)".
> >
> > Quick question: _why_ do you need to join them?  Given that
> > case-fold-search is enabled, couldn't you just use, say, the lower case
> > version?
> 
> 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.
This bug report was last modified 9 years and 172 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.