From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Upcoming loss of usability of Emacs source files and Emacs. Date: Wed, 01 Jul 2015 14:28:57 +0100 Message-ID: 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> <5592A98E.4020407@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1435757377 29738 80.91.229.3 (1 Jul 2015 13:29:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Jul 2015 13:29:37 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 01 15:29:31 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 1ZAI4v-0005Hk-2r for ged-emacs-devel@m.gmane.org; Wed, 01 Jul 2015 15:29:29 +0200 Original-Received: from localhost ([::1]:58483 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAI4u-0004Uj-7L for ged-emacs-devel@m.gmane.org; Wed, 01 Jul 2015 09:29:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAI4o-0004Uc-90 for emacs-devel@gnu.org; Wed, 01 Jul 2015 09:29:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZAI4k-0004ST-S4 for emacs-devel@gnu.org; Wed, 01 Jul 2015 09:29:22 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:35079) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAI4k-0004RH-Kn for emacs-devel@gnu.org; Wed, 01 Jul 2015 09:29:18 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZAI4g-0005Bl-Qn for emacs-devel@gnu.org; Wed, 01 Jul 2015 15:29:14 +0200 Original-Received: from uk.solarflare.com ([193.34.186.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Jul 2015 15:29:14 +0200 Original-Received: from andrewjmoreton by uk.solarflare.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Jul 2015 15:29:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: uk.solarflare.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt) Cancel-Lock: sha1:IMYqdq5lhM8EWTyN8Y89hKWNrv0= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:187696 Archived-At: On Tue 30 Jun 2015, Paul Eggert wrote: > 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. To go off on a tangent slightly, is there a good reason why the documentation is a string containing escapes rather than a sexp using the normal quoting mechanisms ? AndyM