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: [Unicode-2] `C-h f' error
Date: Sun, 02 Dec 2007 16:27:02 -0500
Message-ID: <E1IywL8-0006cL-L4@fencepost.gnu.org>
References: <b4moddycwjv.fsf@jpl.org>
	<E1IrvIu-0000ku-CD@etlken.m17n.org>	<jwvoddykwt5.fsf-monnier+emacs@gnu.org>	<E1IsAFh-0007bu-2U@etlken.m17n.org>
	<b4mejete26t.fsf_-_@jpl.org>	<E1IsHsV-0003yd-Sm@etlken.m17n.org>
	<b4m6404fejy.fsf@jpl.org>	<b4mabpaskl5.fsf@jpl.org>
	<m2myt9jhqa.fsf@news.cyberhut.org>	<b4mbq9nlvf3.fsf@jpl.org>
	<E1IuoTF-0002eR-S6@etlken.m17n.org>
	<yoijve7tvvis.fsf@remote1.student.chalmers.se>
	<E1IwGhc-0004Or-IT@etlken.m17n.org>
Reply-To: rms@gnu.org
NNTP-Posting-Host: lo.gmane.org
Content-Type: text/plain; charset=ISO-8859-15
X-Trace: ger.gmane.org 1196630943 14842 80.91.229.12 (2 Dec 2007 21:29:03 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Sun, 2 Dec 2007 21:29:03 +0000 (UTC)
Cc: emacs-devel@gnu.org, bojohan+news@dd.chalmers.se
To: Kenichi Handa <handa@ni.aist.go.jp>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 02 22:29:12 2007
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 lo.gmane.org with esmtp (Exim 4.50)
	id 1IywNE-0001yJ-5I
	for ged-emacs-devel@m.gmane.org; Sun, 02 Dec 2007 22:29:12 +0100
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1IywMx-0000GF-UN
	for ged-emacs-devel@m.gmane.org; Sun, 02 Dec 2007 16:28:55 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IywLC-0007Am-N3
	for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:06 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IywLA-00079b-Uy
	for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:06 -0500
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IywLA-00079J-Lf
	for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:04 -0500
Original-Received: from fencepost.gnu.org ([140.186.70.10])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <rms@gnu.org>) id 1IywLA-0002ia-83
	for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:04 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60)
	(envelope-from <rms@gnu.org>)
	id 1IywL8-0006cL-L4; Sun, 02 Dec 2007 16:27:02 -0500
In-reply-to: <E1IwGhc-0004Or-IT@etlken.m17n.org> (message from Kenichi Handa
	on Sun, 25 Nov 2007 21:35:12 +0900)
X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4)
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:84504
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/84504>

    >     Fmake_symbol ((!NILP (Vpurify_flag)
    >                    ? make_pure_string (str, len, len, 0)
    >                    : make_string (str, len)));

    > In the make_symbol/Fmake_symbol pair of functions, the Vpurify_flag
    > check is in the former (so is not done after the change); but in the
    > intern/Fintern pair it is in the latter. Isn't this the problem?

    Ah! Perhaps.  But, I don't understand the reason of calling
    make_pure_string always with the last arg multibyte as 0.
    Richard, don't you remember anything?

Not any more.
Sorry.