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 15:41:58 +0000 Message-ID: References: <83lh9lx6oi.fsf@gnu.org> <83a8q1x1cn.fsf@gnu.org> <87h9k74pkw.fsf@gmail.com> <83bnafse4f.fsf@gnu.org> <878u5jrvih.fsf@rub.de> <87mvtyqzyx.fsf@mbork.pl> <831tbaqwwv.fsf@gnu.org> <83k2p2p4ob.fsf@gnu.org> Reply-To: bruce.connor.am@gmail.com 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 1448725330 32505 80.91.229.3 (28 Nov 2015 15:42:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Nov 2015 15:42:10 +0000 (UTC) Cc: emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 28 16:42:03 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 1a2hdT-0008VR-1T for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2015 16:42:03 +0100 Original-Received: from localhost ([::1]:32891 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2hdW-0005Xl-2h for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2015 10:42:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2hdS-0005WU-Gm for emacs-devel@gnu.org; Sat, 28 Nov 2015 10:42:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2hdR-0001c1-EN for emacs-devel@gnu.org; Sat, 28 Nov 2015 10:42:02 -0500 Original-Received: from mail-lf0-x232.google.com ([2a00:1450:4010:c07::232]:32929) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2hdP-0001ar-5l; Sat, 28 Nov 2015 10:41:59 -0500 Original-Received: by lfaz4 with SMTP id z4so154992452lfa.0; Sat, 28 Nov 2015 07:41:58 -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:content-transfer-encoding; bh=7BGWVAqjDeDiofJVoObyRV7s/XeMNKK8+YQJSYKoL+A=; b=f/O/6hD+sVUf1G1uJiHhSSC7+Em1NkNPIajTBkDUZ57AIW9exiM/WdDctur4MF6aKf tEdRvSNboX6xfTZKhlCFjwDWBJSwP+az1DQOBL+wTAP/APNdfGsT+0hmBnhVPzHzt66E dxP7FCGUhitEl9NVh3ZCQkZvoqaT0ik7SAk6LlqdQNd1MxIx6KI4CJZki8qyIBWe6u4I XBuzyh7O5kr9kjyvFL8+JmZnxSr9cV02SSFl885WwfLcJss0HQ7A7XCo9/QGtfwnCR13 HlZFV15ZUaQBNc09xkO/m1knfy/jPr5sQLOC++s4rkN/eyhx06edg0yeBfwnXjXeMdV8 M7+Q== X-Received: by 10.25.18.92 with SMTP id h89mr19221961lfi.54.1448725318389; Sat, 28 Nov 2015 07:41:58 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Sat, 28 Nov 2015 07:41:58 -0800 (PST) In-Reply-To: <83k2p2p4ob.fsf@gnu.org> X-Google-Sender-Auth: MSqKFtBWWNE9ZwgCivxL4LtqgXA 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:195462 Archived-At: 2015-11-28 14:41 GMT+00:00 Eli Zaretskii : >> Date: Sat, 28 Nov 2015 10:23:12 +0000 >> From: Artur Malabarba >> Cc: Stephen Berman , Richard Stallman , >> emacs-devel >> >> Ok. I'm going to work on the char-folding a little bit more today to >> implement support for multi-char matches and to combine it with >> case-folding. Hopefully that will iron out the final inconsistencies. I'm running bootstrap now to make sure I didn't break anything. Then I'll p= ush. > Maybe you could also take a look at this document: > > http://www.unicode.org/reports/tr30/tr30-4.html > > In particular, section 5.2 there mentions several problematic > foldings, which we might consider disabling. For example, the ones > mentioned in 5.2.1 and 5.2.2. Thanks for the pointer. None of those really worry me WRT searching. Char folding is supposed to be convenient at the cost of being unable to distinguish some strings. But I guess they could be a problem for query-replace. Someone replacing 58 with 59 probably doesn't want to replace 5=E2=91=A7 with 59. Since folding is disabled by default on quuery-replace, I think it would be a bit of shame to disable these "risky" foldings completely. Perhaps query-replace could use a different char table, with only a subset. Or it perhaps it would be sufficient to just make this "danger" very clear in the docstring of `replace-character-fold'.