From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: [PATCH] Unicode Lisp reader escapes
Date: Sat, 13 May 2006 00:52:05 -0400
Message-ID: <E1Fem6n-0002Qv-9c@fencepost.gnu.org>
References: <17491.34779.959316.484740@parhasard.net>	<E1FaobM-0005qh-00@etlken>	<ufyjsemrn.fsf@gnu.org>	<E1Fb7ai-0002Yb-00@etlken>	<uy7xjcx5s.fsf@gnu.org>	<87odyfnqcj.fsf-monnier+emacs@gnu.org>	<E1FbSj5-0003RO-00@etlken>	<uk691da3o.fsf@gnu.org>	<17498.27200.911709.330947@parhasard.net>	<e3f682$91m$1@sea.gmane.org>	<E1FcNiN-0004c1-An@fencepost.gnu.org>	<877j4z5had.fsf@gmx.de>	<E1FcbO2-0002U6-0r@fencepost.gnu.org>	<E1FciWf-0007hz-00@etlken>	<87irohfrx1.fsf@gmx.de>	<E1FdEE5-0008RE-Tp@fencepost.gnu.org>	<E1FdKXL-0005lp-00@etlken>	<E1FdfFt-0006ux-Pm@fencepost.gnu.org>	<E1FdhOK-0005JX-00@etlken>
	<E1Fe26h-0007re-Mx@fencepost.gnu.org>	<E1Fe5dw-0005vd-00@etlken>
	<E1FeP3C-0002Jp-JW@fencepost.gnu.org> <E1FeQAp-0003mu-00@etlken>
Reply-To: rms@gnu.org
NNTP-Posting-Host: main.gmane.org
Content-Type: text/plain; charset=ISO-8859-15
X-Trace: sea.gmane.org 1147495969 16120 80.91.229.2 (13 May 2006 04:52:49 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Sat, 13 May 2006 04:52:49 +0000 (UTC)
Cc: alkibiades@gmx.de, emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 13 06:52:46 2006
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
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 1Fem7R-0002qT-Bv
	for ged-emacs-devel@m.gmane.org; Sat, 13 May 2006 06:52:45 +0200
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1Fem7Q-0001GC-VT
	for ged-emacs-devel@m.gmane.org; Sat, 13 May 2006 00:52:44 -0400
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Fem6q-00017c-Jx
	for emacs-devel@gnu.org; Sat, 13 May 2006 00:52:08 -0400
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fem6p-00016n-B9
	for emacs-devel@gnu.org; Sat, 13 May 2006 00:52:07 -0400
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fem6o-00016d-V3
	for emacs-devel@gnu.org; Sat, 13 May 2006 00:52:07 -0400
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fem8i-0002OZ-0H
	for emacs-devel@gnu.org; Sat, 13 May 2006 00:54:04 -0400
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34)
	id 1Fem6n-0002Qv-9c; Sat, 13 May 2006 00:52:05 -0400
Original-To: Kenichi Handa <handa@m17n.org>
In-reply-to: <E1FeQAp-0003mu-00@etlken> (message from Kenichi Handa on Fri, 12
	May 2006 14:26:47 +0900)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=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:54359
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/54359>

    At least you now understand it's not trivial.  Why do you
    think it's worth doing at this stage even if it requires
    nontrivial work?

Because this is a serious cause of unreliability.
It is a bug, or something pretty close to a bug.

    How about just asking users to use emacs-mule coding system
    for *.el files if they want them decoded the same way
    independent of various settings on byte-compiling?

Maybe that is a good enough solution.  Does this solution
solve the whole problem?