From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Change of Lisp syntax for "fancy" quotes in Emacs 27? Date: Tue, 09 Oct 2018 23:57:01 -0400 Message-ID: References: <83y3bc2378.fsf@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1539143729 22289 195.159.176.226 (10 Oct 2018 03:55:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 Oct 2018 03:55:29 +0000 (UTC) Cc: eliz@gnu.org, eggert@cs.ucla.edu, drew.adams@oracle.com, emacs-devel@gnu.org To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 10 05:55:25 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 1gA5am-0005hW-H6 for ged-emacs-devel@m.gmane.org; Wed, 10 Oct 2018 05:55:24 +0200 Original-Received: from localhost ([::1]:54703 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5ct-0004Am-1E for ged-emacs-devel@m.gmane.org; Tue, 09 Oct 2018 23:57:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5cn-00049Y-7G for emacs-devel@gnu.org; Tue, 09 Oct 2018 23:57:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gA5ch-0001Bh-JL for emacs-devel@gnu.org; Tue, 09 Oct 2018 23:57:25 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49124) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5cM-0000xa-3D; Tue, 09 Oct 2018 23:57:02 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1gA5cL-0002Vp-Rx; Tue, 09 Oct 2018 23:57:01 -0400 In-Reply-To: (message from Noam Postavsky on Tue, 9 Oct 2018 10:43:00 -0400) 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:230300 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > The problem is that deciding which characters are confusable and hence > require backslash escaping is based on a shifting mess of heuristics. > So I don't think it's workable to signal a hard error for this. Both > in terms of false positives which could mean possibly breaking code, > and false negatives which means we would be giving a false sense of > security. In principle, that\s a valid point. But can't we assembe a fixed list of characters that are confusable with the usual fonts. and base the warning on that list? We could conceivably have a feature that would check any fontset for confusable characters, and warn the user if it has confusable pairs that are not in the usual list of confusable pairs. -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)