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 21:29:26 +0300 Message-ID: <83a7nr0vzt.fsf@gnu.org> 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> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1538850514 6570 195.159.176.226 (6 Oct 2018 18:28:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Oct 2018 18:28:34 +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 20:28:30 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 1g8rJT-0001Xb-IU for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 20:28:27 +0200 Original-Received: from localhost ([::1]:40063 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8rLa-0007YJ-3a for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 14:30:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8rKt-0007Y0-Sa for emacs-devel@gnu.org; Sat, 06 Oct 2018 14:29:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8rKp-0005E2-Sg for emacs-devel@gnu.org; Sat, 06 Oct 2018 14:29:55 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8rKe-0004wr-4X; Sat, 06 Oct 2018 14:29:40 -0400 Original-Received: from [176.228.60.248] (port=2236 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g8rKd-0002gq-7s; Sat, 06 Oct 2018 14:29:40 -0400 In-reply-to: <5fcbc157-51ac-0814-e470-6e76f76611ac@cs.ucla.edu> (message from Paul Eggert on Sat, 6 Oct 2018 11:03:25 -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:230266 Archived-At: > Cc: emacs-devel@gnu.org, npostavs@users.sourceforge.net > From: Paul Eggert > Date: Sat, 6 Oct 2018 11:03:25 -0700 > > Eli Zaretskii wrote: > > > these examples are not relevant to the issue at hand, > > which is only about quotes > > Quotes are part of the same problem. Yes, but a much smaller part. And solving the problem with quotes doesn't require to solve the more general one. > (ignore-errors (gnus-get-function method 'open-server)) > > Change that APOSTROPHE (U+0027) to RIGHT SINGLE QUOTATION MARK (U+2019) and the > code will look the same but do something quite different, with no diagnostic. 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.