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: Thu, 18 May 2006 22:05:54 -0400 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <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> <87iro4hlox.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 1148004562 28293 80.91.229.2 (19 May 2006 02:09:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 19 May 2006 02:09:22 +0000 (UTC) Cc: storm@cua.dk, emacs-devel@gnu.org, monnier@iro.umontreal.ca, handa@m17n.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 19 04:09:20 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 1FguQZ-0003V8-1V for ged-emacs-devel@m.gmane.org; Fri, 19 May 2006 04:09:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FguQY-0000Yj-02 for ged-emacs-devel@m.gmane.org; Thu, 18 May 2006 22:09:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FguNK-0005xK-Af for emacs-devel@gnu.org; Thu, 18 May 2006 22:05:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FguNJ-0005w5-AY for emacs-devel@gnu.org; Thu, 18 May 2006 22:05:57 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FguNJ-0005vh-1H for emacs-devel@gnu.org; Thu, 18 May 2006 22:05:57 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FguQW-0000X7-CA for emacs-devel@gnu.org; Thu, 18 May 2006 22:09:16 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FguNG-0001nQ-An; Thu, 18 May 2006 22:05:54 -0400 Original-To: Oliver Scholz In-reply-to: <87iro4hlox.fsf@gmx.de> (message from Oliver Scholz on Wed, 17 May 2006 14:37:02 +0200) 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:54752 Archived-At: The C code you wrote to implement byte-compile-no-char-translation might be the right C-level feature. We need Handa to check that, as you said. It should only affect unify-8859-on-decoding-mode, since that's the only one that's relevant to iso-2022. (We decided to give up on stabilizing utf-8 in this way, because too many different variables affect the behavior of utf-8.) However, the right place to set the variable is in find-auto-coding, not in the compiler. Therefore, the variable's name should be changed, since it won't be specific to compilation. It could be stabilize-iso-2022. I can see three possible ways for Lisp files to set this variable: 1. Explicitly. You should specify the variable in the -*- line or the Local Variables list if it matters. 2. Automatically. Whenever a file specifies Emacs-Lisp mode and coding iso-2022, it gets set to t. 3. Both. It gets set to t automatically, but a file can explicitly specify nil. I have another, further suggestion. Rename the variable to unify-8859-on-decoding-mode, and reimplement the function unify-8859-on-decoding-mode to work just by setting the variable. That would be an improvement, since it would mean you can set the mode just by setting the variable.