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: Questions about isearch Date: Fri, 27 Nov 2015 19:52:55 +0200 Message-ID: <83y4djqqh4.fsf@gnu.org> References: <83lh9lx6oi.fsf@gnu.org> <83a8q1x1cn.fsf@gnu.org> <87h9k74pkw.fsf@gmail.com> <83bnafse4f.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 1448646815 1560 80.91.229.3 (27 Nov 2015 17:53:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Nov 2015 17:53:35 +0000 (UTC) Cc: emacs-devel@gnu.org To: bruce.connor.am@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 27 18:53:25 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 1a2ND1-0002He-83 for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2015 18:53:23 +0100 Original-Received: from localhost ([::1]:57939 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2ND3-0000EM-SB for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2015 12:53:25 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2NCr-0000Bb-1T for emacs-devel@gnu.org; Fri, 27 Nov 2015 12:53:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2NCn-0007Gg-R5 for emacs-devel@gnu.org; Fri, 27 Nov 2015 12:53:12 -0500 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:46941) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2NCn-0007Fu-Ix for emacs-devel@gnu.org; Fri, 27 Nov 2015 12:53:09 -0500 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0NYH00H00I9AZA00@a-mtaout21.012.net.il> for emacs-devel@gnu.org; Fri, 27 Nov 2015 19:53:07 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NYH00HGAJ0JW380@a-mtaout21.012.net.il>; Fri, 27 Nov 2015 19:53:07 +0200 (IST) 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.169 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:195398 Archived-At: > Date: Fri, 27 Nov 2015 16:55:45 +0000 > From: Artur Malabarba > Cc: emacs-devel >=20 > > Right, it does. I think I tried "ff", not "f". Is that supposed t= o > > work? >=20 > No. We don't support having multiple characters match a single stri= ng.=20 >=20 > This is a design limitation. We can (and should) discuss improving = this. But > for now I think it should be documented as not supported.=20 Is it reasonable to have =C3=A4 match a=CC=88, but not the other way = around? > - =C3=A4 now finds 'a=CC=88'. Because that is exactly its decomposi= tion.=20 > - =EF=AC=80 doesn't find "ff", because the decomposition of =EF= =AC=80 is not exactly (f f), > it's actually (compat f f). This was a decision, it's not a limitat= ion.=20 So you are saying we support canonical decompositions, but not compatibility decompositions, I see. However, it sounds inconsistent to me, because searching for a does find =E2=93=90, although =E2=93= =90's decomposition is also "not exactly a". I'm afraid it will be hard to explain to th= e users why some of these match, while others don't. Are there any downsides in adding compatibility decompositions to wha= t character folding supports? > I figured that a character should only match its decomposition if t= he > decomposition is strictly made of chars. Otherwise you get things l= ike =C2=B9 > matching 1 (which I thought we didn't want). Well, I think we do want that. At least MS Word does that by default= , so it isn't entirely silly or without precedent.