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, 15 May 2006 16:37:13 -0400 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <17498.27200.911709.330947@parhasard.net> <877j4z5had.fsf@gmx.de> <87irohfrx1.fsf@gmx.de> <87iroarr9i.fsf-monnier+emacs@gnu.org> <87d5egrb4c.fsf-monnier+emacs@gnu.org> <87ves8p0us.fsf-monnier+emacs@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1147725460 22697 80.91.229.2 (15 May 2006 20:37:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 15 May 2006 20:37:40 +0000 (UTC) Cc: emacs-devel@gnu.org, handa@m17n.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 15 22:37:37 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 1Ffjom-0006uC-3B for ged-emacs-devel@m.gmane.org; Mon, 15 May 2006 22:37:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ffjom-00080P-B8 for ged-emacs-devel@m.gmane.org; Mon, 15 May 2006 16:37:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ffjoa-000801-K2 for emacs-devel@gnu.org; Mon, 15 May 2006 16:37:16 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FfjoY-0007zN-UT for emacs-devel@gnu.org; Mon, 15 May 2006 16:37:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FfjoY-0007zC-Qj for emacs-devel@gnu.org; Mon, 15 May 2006 16:37:14 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Ffjr2-000349-CP for emacs-devel@gnu.org; Mon, 15 May 2006 16:39:48 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FfjoX-0000Tn-8c; Mon, 15 May 2006 16:37:13 -0400 Original-To: Stefan Monnier In-reply-to: <87ves8p0us.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 14 May 2006 20:55:50 -0400) 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:54531 Archived-At: > Here's one idea: if the -*- line specifies `coding' and specifies > the mode `emacs-lisp' then force unify-8859-on-decoding to nil > for that file. Forcing it to nil for a particular file is maybe too much work to implement compared to th benefit. What makes it hard? Maybe an easier solution is to add a file-local variable `no-8859-unification' such that if that file is loaded in an Emacs which is configured to use unify-8859-on-decoding it signals an error. Why is it much harder to switch to the nil mode than to signal an error?