From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Questions about isearch Date: Sat, 28 Nov 2015 00:04:33 +0000 Message-ID: References: <83lh9lx6oi.fsf@gnu.org> <83a8q1x1cn.fsf@gnu.org> <87h9k74pkw.fsf@gmail.com> <83bnafse4f.fsf@gnu.org> <878u5jrvih.fsf@rub.de> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c3b13e857a1b05258e8dc0 X-Trace: ger.gmane.org 1448669082 32543 80.91.229.3 (28 Nov 2015 00:04:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Nov 2015 00:04:42 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel To: Stephen Berman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 28 01:04:39 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 1a2T0H-000741-Ha for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2015 01:04:37 +0100 Original-Received: from localhost ([::1]:58985 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2T0K-00026x-AM for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2015 19:04:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2T0H-000260-98 for emacs-devel@gnu.org; Fri, 27 Nov 2015 19:04:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2T0G-00084x-9C for emacs-devel@gnu.org; Fri, 27 Nov 2015 19:04:37 -0500 Original-Received: from mail-lf0-x232.google.com ([2a00:1450:4010:c07::232]:32813) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2T0E-00084k-Cs; Fri, 27 Nov 2015 19:04:34 -0500 Original-Received: by lfaz4 with SMTP id z4so143092596lfa.0; Fri, 27 Nov 2015 16:04:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hJtYYG3FhArd7u2K8zDcTajQMYJ94ZS40KIn6fXTIvY=; b=aAjkDjjuT4qoWP7ToMN+mdFscI4p7QYZp8AkUa7BtlwoTlbRTC42gRJZCWawr7clNn pXfmedc1IUJO97tDC1V4oLNARaThuBGSgvc5926bQeiiFTFlafUQjY7Ms2zMR8Ah2cAz R6Cc0Rx7JPb6RHExiHuY/6qgLLLHcFuMonwAi4OV8+6/JQ8dDLDstnJazXV3By0SPLHt XTuGb4ocRwaw2h8oOO6gvGmEl2krqpkIxKHEyZdF8gpvIdzU9VT0BSnOG/a6Aqoo4PNd sdRNh8T2rMYeS4wjKqBQxLiYR2Sh40WK1EYFD9z8el9ykYuuqzWVkTUcAPuf179JCMdy tA1g== X-Received: by 10.112.13.66 with SMTP id f2mr11329270lbc.79.1448669073469; Fri, 27 Nov 2015 16:04:33 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Fri, 27 Nov 2015 16:04:33 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Fri, 27 Nov 2015 16:04:33 -0800 (PST) In-Reply-To: <878u5jrvih.fsf@rub.de> X-Google-Sender-Auth: vIBFrH4CiYhbbWVxbIOgxq_u-W0 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c07::232 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:195424 Archived-At: --001a11c3b13e857a1b05258e8dc0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 27 Nov 2015 9:18 pm, "Stephen Berman" wrote: > > No. We don't support having multiple characters match a single string. > > Is this why "ss" does not match the German letter "=C3=9F"? Indeed. > I assume the > reason "s" does not match "=C3=9F" is that the latter does not have a > decomposition including "s", whereas the decomposition of e.g. "=EF=AC=80= " does > include "f", correct? Yes. > In fact, looking at the value of character-fold-table, it seems to me > that the current implementation of folding based on character > decomposition often yields surprising results: e.g. "f" matches not only > "=EF=AC=80" but also "=E3=8E=99" and "=EF=AC=84", but "m" and "l" fail to= match the latter two, > respectively. This was by choice, and it would be trivial to change. Do others find it surprising? > Another shortcoming is that the decompositions do not respect > case-folding, e.g. "f" fails to match "=E2=84=B1" and "=E2=84=BB" (with c= ase-folding > enabled), whereas "F" does match them, but fails to match "=EF=AC=80". True. This can be fixed, I think. Could you file a bug report so we don't forget? --001a11c3b13e857a1b05258e8dc0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 27 Nov 2015 9:18 pm, "Stephen Berman" <stephen.berman@gmx.net> wrote:<= br> > > No. We don't support having multiple characters match a singl= e string.
>
> Is this why "ss" does not match the German letter "=C3= =9F"?=C2=A0

Indeed.

> I assume the
> reason "s" does not match "=C3=9F" is that the lat= ter does not have a
> decomposition including "s", whereas the decomposition of e.= g. "=EF=AC=80" does
> include "f", correct?=C2=A0

Yes.

> In fact, looking at the value of character-fold-table, = it seems to me
> that the current implementation of folding based on character
> decomposition often yields surprising results: e.g. "f" matc= hes not only
> "=EF=AC=80" but also "=E3=8E=99" and "=EF=AC= =84", but "m" and "l" fail to match the latter two= ,
> respectively.=C2=A0

This was by choice, and it would be trivial to change. Do ot= hers find it surprising?

> Another shortcoming is that the decompositions do not r= espect
> case-folding, e.g. "f" fails to match "=E2=84=B1" = and "=E2=84=BB" (with case-folding
> enabled), whereas "F" does match them, but fails to match &q= uot;=EF=AC=80".

True. This can be fixed, I think. Could you file a bug repor= t so we don't forget?

--001a11c3b13e857a1b05258e8dc0--