From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Garreau\, Alexandre" Newsgroups: gmane.emacs.devel Subject: Re: Change of Lisp syntax for "fancy" quotes in Emacs 27? Date: Sat, 06 Oct 2018 21:32:49 +0200 Message-ID: <1eb2wszzzzzz.7ne.xxuns.g6.gal@portable.galex-713.eu> References: <83y3bc2378.fsf@gnu.org> <83k1mv1j1b.fsf@gnu.org> <5ebde087-561e-c71a-0840-d99626c02dcf@cs.ucla.edu> <83bm8710ss.fsf@gnu.org> <5fcbc157-51ac-0814-e470-6e76f76611ac@cs.ucla.edu> <83a7nr0vzt.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1538854308 17555 195.159.176.226 (6 Oct 2018 19:31:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Oct 2018 19:31:48 +0000 (UTC) User-Agent: Gnus (5.13), GNU Emacs 25.1.1 (i686-pc-linux-gnu) Cc: Paul Eggert , emacs-devel@gnu.org, npostavs@users.sourceforge.net To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 06 21:31:43 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 1g8sIh-0004Tu-PW for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 21:31:43 +0200 Original-Received: from localhost ([::1]:40200 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8sKo-0004EL-1C for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 15:33:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40447) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8sK6-0004E0-JI for emacs-devel@gnu.org; Sat, 06 Oct 2018 15:33:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8sK5-00044N-FP for emacs-devel@gnu.org; Sat, 06 Oct 2018 15:33:10 -0400 Original-Received: from portable.galex-713.eu ([2a00:5884:8305::1]:58144) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g8sK5-00042U-0G; Sat, 06 Oct 2018 15:33:09 -0400 Original-Received: from localhost ([::1] helo=portable.galex-713.eu) by portable.galex-713.eu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8sJy-0000WI-0d; Sat, 06 Oct 2018 21:33:02 +0200 X-GPG-FINGERPRINT: E109 9988 4197 D7CB B0BC 5C23 8DEB 24BA 867D 3F7F X-Accept-Language: fr, en, it, eo In-Reply-To: <83a7nr0vzt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Oct 2018 21:29:26 +0300") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:5884:8305::1 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:230269 Archived-At: On 2018-10-06 at 21:29, Eli Zaretskii wrote: > I understand. I'm just saying that adding a backslash between the > U+2019 quote will not significantly improve the situation, because > Emacs Lisp uses backslashes in many other situation, like ?\", and > therefore the mere fact that there is a backslash doesn't necessarily > alert the human reader to the existence of an unusual character. I think what is wanted here is not to alert of unusual character but alert of a non-syntaxically-relevant (for the reader) character, such as ?\', which quotes (or be it ?\", or ?\(, or ?\), etc.), which looks like a character that will have syntactic consequences (like quoting), while being a =E2=80=9Cnormal=E2=80=9D (part of the symbol) character. Like not = alerting two symbols may look alike (the =D5=9Aopen-server/=C2=B4open-server case), but = one thing which is a symbol, unquoted (like \'open-server, which is evident it=E2=80=99s a symbol because of the backslash, since afaik no character preceded by a backslash can do something with syntax, apart being part of a symbol (thus the behavior is clear)), and the other which *not* be a unquoted symbol at all (like 'open-server, which just returns the symbol). I guess the same issue indeed arise with ?=C2=B8, or anything alike, that won=E2=80=99t unquote the next symbol.