From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Tue, 16 May 2006 16:24:54 +0200 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 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1147789996 22844 80.91.229.2 (16 May 2006 14:33:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 16 May 2006 14:33:16 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 16 16:33:11 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 1Fg0Vm-0004dD-4J for ged-emacs-devel@m.gmane.org; Tue, 16 May 2006 16:26:59 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fg0Vl-0004iy-I2 for ged-emacs-devel@m.gmane.org; Tue, 16 May 2006 10:26:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fg0VZ-0004im-Sw for emacs-devel@gnu.org; Tue, 16 May 2006 10:26:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fg0VX-0004gj-Tw for emacs-devel@gnu.org; Tue, 16 May 2006 10:26:45 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fg0VX-0004ge-LY for emacs-devel@gnu.org; Tue, 16 May 2006 10:26:43 -0400 Original-Received: from [195.41.46.237] (helo=pfepc.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fg0Y5-0004Hq-TG; Tue, 16 May 2006 10:29:22 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (unknown [80.165.4.124]) by pfepc.post.tele.dk (Postfix) with SMTP id 1A90E8A0054; Tue, 16 May 2006 16:26:30 +0200 (CEST) Original-To: Oliver Scholz In-Reply-To: <87y7x289lr.fsf@gmx.de> (Oliver Scholz's message of "Tue, 16 May 2006 13:58:24 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:54577 Archived-At: Oliver Scholz writes: > storm@cua.dk (Kim F. Storm) writes: > >> Oliver Scholz writes: >> >>> We are discussing a *very* special case here; it affects only Emacs >>> Lisp source files, because compilation of those, so to say, "freezes" >>> the particular settings for unification/fragmentation in the *.elc >>> file. >> >> I really wonder why this has suddenly become such a big issue. >> >> In practice, these things have worked fine for ages, so why bother _now_ >> when we should focus on finalizing the release of 22.1 ? > > Unification and UCS fragmentation are new in Emacs 22. But Emacs 22 already has a large user community, and I don't recall anyone actually complaining about it! > > [...] >> I would suggest to leave the entire issue for after the release! > > I agree, in principle. IIRC, I was the first one here to suggest to > just document the issue and be done with it. But documenting it would > be a good idea. Indeed. > Something along the lines: "When using non-ASCII > characters in Emacs Lisp source files, beware that compilation > "freezes" some of your current settings for character unification > and/or fragmentation. This might exactly be what you want. But if you > compile Emacs Lisp files with the intention to give the compiled files > to other users, you should make sure that the following settings are > at their default value: ..." Is this a problem for any of the lisp files included in CVS emacs ?? Then it could be a problem wrt distribution pre-built versions. Otherwise, I still think it is better left alone -- and documented as you suggested (or simply advise against distributing such files to anybody and let them compile the files themselves). Could the byte-compiler warn if it encounters a non-ascii character that may cause problems? -- Kim F. Storm http://www.cua.dk