From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Change of Lisp syntax for "fancy" quotes in Emacs 27? Date: Tue, 09 Oct 2018 19:13:11 +0300 Message-ID: <834ldvyu7c.fsf@gnu.org> References: <83y3bc2378.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1539101489 7498 195.159.176.226 (9 Oct 2018 16:11:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 9 Oct 2018 16:11:29 +0000 (UTC) Cc: emacs-devel@gnu.org, drew.adams@oracle.com, npostavs@users.sourceforge.net To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 09 18:11:25 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9ubV-0001rV-5x for ged-emacs-devel@m.gmane.org; Tue, 09 Oct 2018 18:11:25 +0200 Original-Received: from localhost ([::1]:52792 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9udb-0007zI-BZ for ged-emacs-devel@m.gmane.org; Tue, 09 Oct 2018 12:13:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55417) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9udV-0007z0-BI for emacs-devel@gnu.org; Tue, 09 Oct 2018 12:13:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9udU-0007fY-M9 for emacs-devel@gnu.org; Tue, 09 Oct 2018 12:13:29 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36341) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9udJ-0007XX-Fb; Tue, 09 Oct 2018 12:13:19 -0400 Original-Received: from [176.228.60.248] (port=3216 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g9udH-0000cF-UI; Tue, 09 Oct 2018 12:13:17 -0400 In-reply-to: (message from Paul Eggert on Tue, 9 Oct 2018 08:30:22 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:230290 Archived-At: > Cc: Eli Zaretskii , Emacs developers , > Drew Adams > From: Paul Eggert > Date: Tue, 9 Oct 2018 08:30:22 -0700 > > Noam Postavsky wrote: > > deciding which characters are confusable and hence > > require backslash escaping is based on a shifting mess of heuristics. > > No more than the "shifting mess of heuristics" inevitable in any choice of > syntax. Quite possibly the confusables list from the Unicode consortium will do. > The list won't shift much once it's established. > > We can start merely by warning about confusable characters and seeing how often > those warnings are triggered in real (as opposed to malicious or > purposely-tricky) code. If the warnings are quite rare, in a later Emacs version > we can change the manual from "confusable characters should be escaped" to > "confusable characters must be escaped". Confusable characters are confusable only when they are surrounded by ASCII characters or by characters that look like ASCII. By themselves, at least many of them, are entirely legitimate. For example, I see no reason to warn about a symbol named "сталин", even though the characters с and а will be considered confusables if the symbol would be named something like "саn". So I think we cannot go by characters here, we need to examine the context. That is why I think we shouldn't link this particular issue, of quote characters, with the more general problem: the latter is much more complicated to solve correctly.