GNU bug report logs - #9608
24.0.50; Emacs lisp reader thinks no-break space is 0x08a0 (should be 0x00a0)

Previous Next

Package: emacs;

Reported by: "David M. Cooke" <david.m.cooke <at> gmail.com>

Date: Tue, 27 Sep 2011 00:03:02 UTC

Severity: normal

Found in version 24.0.50

Done: Andreas Schwab <schwab <at> linux-m68k.org>

Bug is archived. No further changes may be made.

Full log

Message #10 received at 9608-done <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: "David M. Cooke" <david.m.cooke <at> gmail.com>
Cc: 9608-done <at> debbugs.gnu.org
Subject: Re: bug#9608: 24.0.50;
	Emacs lisp reader thinks no-break space is 0x08a0 (should be 0x00a0)
Date: Tue, 27 Sep 2011 10:44:26 +0200

"David M. Cooke" <david.m.cooke <at> gmail.com> writes:

> The changes to the whitespace handling were introduced in bzr revision
> 78902 (on 2007-07-30, which is a few weeks after a discussion about
> handling NO-BREAK SPACE on the mailing list).

That was before the unicode merge.

> I'm guessing using 0x8a0 was just a thinko.

No, it was the correct number at that time, when Emacs used the mule
encoding internally.

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
This bug report was last modified 13 years and 238 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.