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: Sat, 06 Oct 2018 19:45:39 +0300 Message-ID: <83bm8710ss.fsf@gnu.org> References: <83y3bc2378.fsf@gnu.org> <83k1mv1j1b.fsf@gnu.org> <5ebde087-561e-c71a-0840-d99626c02dcf@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1538844260 9095 195.159.176.226 (6 Oct 2018 16:44:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Oct 2018 16:44:20 +0000 (UTC) Cc: npostavs@users.sourceforge.net, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 06 18:44:16 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 1g8pgd-0002A1-RZ for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 18:44:15 +0200 Original-Received: from localhost ([::1]:39833 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8pie-0004bW-Si for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 12:46:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8piY-0004bC-II for emacs-devel@gnu.org; Sat, 06 Oct 2018 12:46:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8piT-00027j-6V for emacs-devel@gnu.org; Sat, 06 Oct 2018 12:46:14 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54624) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8piC-0001wQ-6Y; Sat, 06 Oct 2018 12:45:52 -0400 Original-Received: from [176.228.60.248] (port=3426 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g8piB-0005bL-OW; Sat, 06 Oct 2018 12:45:52 -0400 In-reply-to: <5ebde087-561e-c71a-0840-d99626c02dcf@cs.ucla.edu> (message from Paul Eggert on Sat, 6 Oct 2018 08:51:18 -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:230264 Archived-At: > From: Paul Eggert > Cc: emacs-devel@gnu.org, Noam Postavsky > Date: Sat, 6 Oct 2018 08:51:18 -0700 > > Eli Zaretskii wrote: > > I agree that viewing ELisp code outside of Emacs is a valid use case. > > But I don't think a backslash before these non-ASCII quotes will > > significantly lower the confusion potential when those characters are > > used in the source. > > I don't follow. If someone writes '(let ((foo\ bar)) baz)' then a human reader > is put immediately and obviously on notice that there's something odd about that > code. We already require a backslash for that ordinary space (U+0020); why not > also require it for EN SPACE (U+2002)? That will significantly lower confusion here. How will it lower the confusion, when the same is required for a space? And once again, these examples are not relevant to the issue at hand, which is only about quotes. > > I don't see how > > we can be harsh to uses of these characters without actually > > prohibiting their use in symbols. > > I already gave one proposal for doing just that: require that characters > confusable with ASCII be escaped. That's an annoyance, IMO. This is why this bug report exists, right? And again, please don't bring up the more general issue with any other confusable character, as those require a more general solution about which we don't yet have a clear idea.