From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: ASCII-folded search [was: Re: Upcoming loss of usability ...] Date: Tue, 23 Jun 2015 19:46:14 +0300 Message-ID: <83si9ifk4p.fsf@gnu.org> References: <20150615142237.GA3517@acm.fritz.box> <87y4jkhqh5.fsf@uwakimon.sk.tsukuba.ac.jp> <557F3C22.4060909@cs.ucla.edu> <5580D356.4050708@cs.ucla.edu> <87si9qonxb.fsf@gnu.org> <87ioamz8if.fsf@petton.fr> <32013464-2300-46c6-ba46-4a3c36bfee5d@default> <87twu62nnt.fsf@mbork.pl> <87oakdfwim.fsf@uwakimon.sk.tsukuba.ac.jp> <83wpz1lh7c.fsf@gnu.org> <83oakdl7yj.fsf@gnu.org> <83ioall3x5.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1435078015 1812 80.91.229.3 (23 Jun 2015 16:46:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jun 2015 16:46:55 +0000 (UTC) Cc: stephen@xemacs.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: bruce.connor.am@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 23 18:46:46 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z7RLS-00064B-3i for ged-emacs-devel@m.gmane.org; Tue, 23 Jun 2015 18:46:46 +0200 Original-Received: from localhost ([::1]:46426 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7RLR-0004dF-J0 for ged-emacs-devel@m.gmane.org; Tue, 23 Jun 2015 12:46:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7RLG-0004RF-H8 for emacs-devel@gnu.org; Tue, 23 Jun 2015 12:46:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7RLA-0000xu-MS for emacs-devel@gnu.org; Tue, 23 Jun 2015 12:46:34 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:55972) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7RLA-0000wS-F5 for emacs-devel@gnu.org; Tue, 23 Jun 2015 12:46:28 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NQE00L00P13Y000@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Tue, 23 Jun 2015 19:46:27 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NQE00LG7P9EXZ10@a-mtaout20.012.net.il>; Tue, 23 Jun 2015 19:46:27 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:187428 Archived-At: > Date: Mon, 22 Jun 2015 22:02:11 +0100 > From: Artur Malabarba > Cc: emacs-devel , Stefan Monnier ,=20 > =09Stephen Turnbull >=20 > By the way, here's a patch of how the regexp version can apply to b= oth > isearch and query-replace while doing pretty much everything that's > been requested. > It fixes the issues raised by Eli, and (unlike the previous version= ) > is now fully implemented. > Now, "a" will match any character whose decomposition has "a" as th= e > first letter character (not necessarily the first character), so it > will match =E2=92=9C, for instance. "a" also matches the decomposit= ion itself, > so it will match both the letter "=C3=A1" and the two-character com= bo "a=CC=81". > Note that the unicode characters still only match themselves, becau= se > that's also how case-folding works (if you search uppercase you onl= y > match uppercase). >=20 > I believe that is all we were asking for, correct? Yes. But I'd still want to know what would it take to make this applicable to other types of search. > Shall I merge? Fine with me, but please wait until we clarify the issue with non-incremental search. Thanks. > (It adds about 5 seconds of compile time in my laptop) Doesn't sound too bad to me.