From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Tue, 23 May 2006 10:05:56 +0900 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> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1148346426 24440 80.91.229.2 (23 May 2006 01:07:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 23 May 2006 01:07:06 +0000 (UTC) Cc: alkibiades@gmx.de, storm@cua.dk, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 23 03:07:02 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 1FiLMN-0007Qk-LF for ged-emacs-devel@m.gmane.org; Tue, 23 May 2006 03:06:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiLMN-00087p-6D for ged-emacs-devel@m.gmane.org; Mon, 22 May 2006 21:06:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FiLMA-00085P-CE for emacs-devel@gnu.org; Mon, 22 May 2006 21:06:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FiLM8-000815-Ao for emacs-devel@gnu.org; Mon, 22 May 2006 21:06:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiLM8-00080i-3w for emacs-devel@gnu.org; Mon, 22 May 2006 21:06:40 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FiLQD-00074i-7W; Mon, 22 May 2006 21:10:53 -0400 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k4N16K5c030994; Tue, 23 May 2006 10:06:20 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k4N15vus007060; Tue, 23 May 2006 10:06:19 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FiLLQ-0003MG-00; Tue, 23 May 2006 10:05:56 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Mon, 22 May 2006 11:12:18 -0400) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:55093 Archived-At: In article , Richard Stallman writes: > 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. At least, this should work for people who don't mind the cumbersomeness. > Another way is that specification of coding: together with mode: > emacs-lisp could do this automatically. I object to this because it's an incompatible change that should be avoided at this stage. In addition, we then have to invent someway to "enable" normal character translation. > Another way is that you could specify coding: in a special way, > perhaps with ! at the end of the coding system name. I don't know if that is aesthetically good, but at least it's a quite handy way. ;; xxx.el -- Do XXX. -*- coding: latin-1!; -*- So, I'd like to implement both the 1st and 3rd method. Ok? --- Kenichi Handa handa@m17n.org