From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Change of Lisp syntax for "fancy" quotes in Emacs 27? Date: Fri, 2 Feb 2018 14:52:09 -0800 Organization: UCLA Computer Science Department Message-ID: <16831945-e0fb-ab64-fc31-2534adf7bcf8@cs.ucla.edu> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1517611875 19241 195.159.176.226 (2 Feb 2018 22:51:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Feb 2018 22:51:15 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 Cc: Drew Adams To: Noam Postavsky , Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 02 23:51:11 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 1ehkAZ-0003qw-Dy for ged-emacs-devel@m.gmane.org; Fri, 02 Feb 2018 23:50:55 +0100 Original-Received: from localhost ([::1]:39047 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehkCa-0003ZG-Al for ged-emacs-devel@m.gmane.org; Fri, 02 Feb 2018 17:53:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehkBs-0003YR-Gp for emacs-devel@gnu.org; Fri, 02 Feb 2018 17:52:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehkBo-0002Bg-JY for emacs-devel@gnu.org; Fri, 02 Feb 2018 17:52:16 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:50706) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ehkBo-0002B5-Cf for emacs-devel@gnu.org; Fri, 02 Feb 2018 17:52:12 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 12C9116157F; Fri, 2 Feb 2018 14:52:11 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id hDsBmZQw2eF4; Fri, 2 Feb 2018 14:52:10 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 0EBA21615C9; Fri, 2 Feb 2018 14:52:10 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id CymzADluSPFW; Fri, 2 Feb 2018 14:52:09 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id E91181615BA; Fri, 2 Feb 2018 14:52:09 -0800 (PST) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:222442 Archived-At: On 02/02/2018 02:24 PM, Noam Postavsky wrote: > In Bug#30217, Drew Adams strongly objects to this change. I don't want > to "sneak" this in, so I'm asking here for people's thoughts on this. I see two main categories of users here, with different needs.=20 Less-expert users are likely to run into problems with quotes and other=20 characters (that's why we got bug reports), and appreciate diagnostics=20 pinpointing the problems; also, programmers concerned about security are=20 likely to want these confusing characters to be diagnosed, to prevent an=20 attacker from sending code that is easily read one way but actually=20 operates in a different way. On the other hand, programs that generate=20 Elisp code might prefer not having to special-case these characters. So=20 perhaps there should be a buffer-local variable that controls which=20 behavior is selected. The default behavior should be the one that caters=20 better to general users and is safer. While we're on the topic, I suggest using the Unicode confusables list=20 to come=20 up with a list of confusing alternatives for each character that has a=20 special meaning in Emacs Lisp. This should be better than our trying to=20 come up with our own, ad-hoc list. For example, U+A78C LATIN SMALL=20 LETTER SALTILLO (=EA=9E=8C) looks almost exactly like an apostrophe on my= screen=20 and is in the confusables list, but is not a character that Emacs=20 currently checks for.