From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Upcoming loss of usability of Emacs source files and Emacs. Date: Tue, 30 Jun 2015 07:37:02 -0700 Organization: UCLA Computer Science Department Message-ID: <5592A98E.4020407@cs.ucla.edu> References: <20150615142237.GA3517@acm.fritz.box> <87y4jkhqh5.fsf@uwakimon.sk.tsukuba.ac.jp> <557F3C22.4060909@cs.ucla.edu> <5580D356.4050708@cs.ucla.edu> <87si9qonxb.fsf@gnu.org> <5581C29E.1030101@yandex.ru> <558D6A3D.1070706@yandex.ru> <558DD6EA.4090306@yandex.ru> <558F497A.8050304@yandex.ru> <55926A9E.40901@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1435675045 19553 80.91.229.3 (30 Jun 2015 14:37:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 30 Jun 2015 14:37:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 30 16:37:16 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z9wex-00072m-Jj for ged-emacs-devel@m.gmane.org; Tue, 30 Jun 2015 16:37:15 +0200 Original-Received: from localhost ([::1]:47340 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9wex-0007F5-3A for ged-emacs-devel@m.gmane.org; Tue, 30 Jun 2015 10:37:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9wes-0007Cn-9o for emacs-devel@gnu.org; Tue, 30 Jun 2015 10:37:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9wem-0006Pn-BB for emacs-devel@gnu.org; Tue, 30 Jun 2015 10:37:10 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:36589) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9wem-0006PY-4d for emacs-devel@gnu.org; Tue, 30 Jun 2015 10:37:04 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 5FAD5160176; Tue, 30 Jun 2015 07:37:03 -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 POs3dFQpO1hx; Tue, 30 Jun 2015 07:37:02 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id AFC1B16081B; Tue, 30 Jun 2015 07:37:02 -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 fUtceCFid2uW; Tue, 30 Jun 2015 07:37:02 -0700 (PDT) Original-Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 8E80E160176; Tue, 30 Jun 2015 07:37:02 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 In-Reply-To: <55926A9E.40901@yandex.ru> 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.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:187674 Archived-At: Dmitry Gutov wrote: > > The font-lock solution has other benefits; it could implement a different scheme > (or delegate the escaping step to substitute-command-keys, which seems a fine > idea now, actually). But it currently uses the syntax that's been requested: "\\~". I thought that font-lock couldn't use the same escape syntax that substitute-command-keys does, and that this was why you suggested \~ rather than \= -- i.e., so that one could use \= to escape characters that substitute-command-keys would otherwise interpret, and use \~ to escape characters that font-lock would otherwise interpret. It would be better to use the one escape syntax, as it's one less thing to explain to Emacs users. But how would it work? I don't see how.