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: Sat, 6 Oct 2018 12:18:53 -0700 Organization: UCLA Computer Science Department Message-ID: <2742598a-3e4f-5391-5355-4adf10375d09@cs.ucla.edu> 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; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1538853459 22493 195.159.176.226 (6 Oct 2018 19:17:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Oct 2018 19:17:39 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 Cc: 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:17:35 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 1g8s50-0005j8-Ok for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 21:17:34 +0200 Original-Received: from localhost ([::1]:40169 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8s77-0000e9-CO for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 15:19:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37697) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8s6V-0000dq-Df for emacs-devel@gnu.org; Sat, 06 Oct 2018 15:19:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8s6U-0005oY-Le for emacs-devel@gnu.org; Sat, 06 Oct 2018 15:19:07 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:37846) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g8s6N-0005ci-QD; Sat, 06 Oct 2018 15:18:59 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 5E63B1616D5; Sat, 6 Oct 2018 12:18:57 -0700 (PDT) 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 EWxe4yB2rZoA; Sat, 6 Oct 2018 12:18:54 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 3FEF31616EF; Sat, 6 Oct 2018 12:18:54 -0700 (PDT) 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 JOvbc07jYW9C; Sat, 6 Oct 2018 12:18:54 -0700 (PDT) Original-Received: from [192.168.1.9] (cpe-23-242-74-103.socal.res.rr.com [23.242.74.103]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 1873D1616D5; Sat, 6 Oct 2018 12:18:54 -0700 (PDT) In-Reply-To: <83a7nr0vzt.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x 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:230267 Archived-At: Eli Zaretskii wrote: > 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. Yes, the solution I proposed addresses only symbols, not the more-general= =20 problem of confusable characters in strings and characters. Although symb= ols are=20 a more significant issue since they occur more often, it would be nice to= =20 address strings and character constants too. We can do that by adding sup= port=20 for a new string escape \cX for the confusable character X (e.g., ?\c=D5=9A= would=20 mean U+055A ARMENIAN APOSTROPHE), and by diagnosing the use of unescaped=20 confusable characters in strings and character constants.