From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Mon, 22 May 2006 11:12:18 -0400 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87irohfrx1.fsf@gmx.de> <87iroarr9i.fsf-monnier+emacs@gnu.org> <87d5egrb4c.fsf-monnier+emacs@gnu.org> <87ves8p0us.fsf-monnier+emacs@gnu.org> <87ves8ngtb.fsf@gmx.de> <87u07qcnaa.fsf@gmx.de> <87y7x289lr.fsf@gmx.de> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1148310894 21163 80.91.229.2 (22 May 2006 15:14:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 22 May 2006 15:14:54 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, storm@cua.dk, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 22 17:14:53 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FiC74-00038p-RS for ged-emacs-devel@m.gmane.org; Mon, 22 May 2006 17:14:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiC74-000590-30 for ged-emacs-devel@m.gmane.org; Mon, 22 May 2006 11:14:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FiC4x-00046x-L0 for emacs-devel@gnu.org; Mon, 22 May 2006 11:12:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FiC4w-00046C-Rc for emacs-devel@gnu.org; Mon, 22 May 2006 11:12:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiC4w-00045t-N7 for emacs-devel@gnu.org; Mon, 22 May 2006 11:12:18 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FiC8x-00011j-Lk for emacs-devel@gnu.org; Mon, 22 May 2006 11:16:27 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FiC4w-00075E-2u; Mon, 22 May 2006 11:12:18 -0400 Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Mon, 22 May 2006 10:33:48 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:55059 Archived-At: So, disabling character translation on reading an iso-2022 *.el file effectively stabilize the byte-compiling of the file without any actual problem. Ok, I am convinced that disabling character translation is a good solution _mechanism_. The remaining question is what user interface to use. That is, how should Emacs determine that it should set enable-character-translation to nil for these files? One obvious way is an explicit specification of the variable enable-character-translation. But that would be cumbersome to use. Another way is that specification of coding: together with mode: emacs-lisp could do this automatically. Another way is that you could specify coding: in a special way, perhaps with ! at the end of the coding system name. What do you think?