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, 08 May 2006 18:29:13 -0400 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> <17498.27200.911709.330947@parhasard.net> <877j4z5had.fsf@gmx.de> <87irohfrx1.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 1147127378 18812 80.91.229.2 (8 May 2006 22:29:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 8 May 2006 22:29:38 +0000 (UTC) Cc: alkibiades@gmx.de, emacs-devel@gnu.org, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 09 00:29:36 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 1FdEEQ-0001qx-Ui for ged-emacs-devel@m.gmane.org; Tue, 09 May 2006 00:29:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdEEQ-0005He-Es for ged-emacs-devel@m.gmane.org; Mon, 08 May 2006 18:29:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FdEE8-0005CE-S6 for emacs-devel@gnu.org; Mon, 08 May 2006 18:29:16 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FdEE7-0005Ao-H5 for emacs-devel@gnu.org; Mon, 08 May 2006 18:29:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdEE7-0005Ag-49 for emacs-devel@gnu.org; Mon, 08 May 2006 18:29:15 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FdEF2-0007gK-Lp for emacs-devel@gnu.org; Mon, 08 May 2006 18:30:12 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FdEE5-0008RE-Tp; Mon, 08 May 2006 18:29:14 -0400 Original-To: Oliver Scholz In-reply-to: <87irohfrx1.fsf@gmx.de> (message from Oliver Scholz on Sun, 07 May 2006 23:26: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:54110 Archived-At: As Richard wrote, the fix would be to change the settings to their default, unless the files set a specific variable. But given the work this would require and given that the value of changing the defaults is IMO somewhat dubious, you could as well just document it in etc/PROBLEMS. We seem to be talking about two variables here: unify-8859-on-decoding-mode and utf-fragment-on-decoding. Are there any others involved? I do not know what those variables mean. Do they affect the choice of coding system? Or do they take effect by altering the meaning of a given coding system? If it is the former, the Lisp source file can defend against this problem by specifying coding in the -*- line. We tell people to do this in Lisp source files. If it is the latter, there are two possible solutions: 1. to make the compiler bind these variables to their default values. 2. to tell people that all Lisp files for which this is relevant should specify these variables explicitly. If it is just those two variables, I think #1 is easy and preferable. Are there any other variables for which this arises?