GNU bug report logs - #1935
describe-char does not show raw bytes as such

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Juanma Barranquero <lekktu <at> gmail.com>
Subject: bug#1935 closed by Kenichi Handa <handa <at> m17n.org> (Re: [EMACS] 
 categories in output of `describe-char')
Date: Tue, 20 Jan 2009 06:15:03 +0000

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the emacs package:

#1935: describe-char does not show raw bytes as such

It has been closed by Kenichi Handa <handa <at> m17n.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Kenichi Handa <handa <at> m17n.org> by
replying to this email.


-- 
1935: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1935
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Kenichi Handa <handa <at> m17n.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 1935-done <at> debbugs.gnu.org, handa <at> m17n.org
Subject: Re: [EMACS] categories in output of `describe-char'
Date: Tue, 20 Jan 2009 15:08:33 +0900

In article <f7ccd24b0901190754m1a319ad2m97a9d0072a29da40 <at> mail.gmail.com>, Juanma Barranquero <lekktu <at> gmail.com> writes:

> On Mon, Jan 19, 2009 at 12:12, Juanma Barranquero <lekktu <at> gmail.com> wrote:
> > OK, I'll work on it.

> Applied.

Thank you.

> Somewhat related: did you see bug#1935?

Ah, I've just installed a fix.

---
Kenichi Handa
handa <at> m17n.org

[Message part 3 (message/rfc822, inline)]

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Emacs developers <emacs-devel <at> gnu.org>,
        Emacs Bug Tracker <submit <at> debbugs.gnu.org>
Subject: Re: No coding system in the modeline for unibyte buffers.
Date: Sat, 17 Jan 2009 03:24:41 +0100

On Sat, Jan 17, 2009 at 03:11, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:

> Actually the raw-text part of a multibyte buffer only affects operation
> when it is saved and loaded, so it can contain characters that are
> not bytes.

Yes, I understand that.

>> But I confess I'm puzzled why
>
>>  M-x find-file-binary test.txt <RET>
>>  M-: enable-multibyte-characters <RET>  => nil
>>  C-u C-x =    ; over ñ
>
>>         character:   (241, #o361, #xf1)
>> preferred charset: iso-8859-1 (Latin-1 (ISO/IEC 8859-1))
>>        code point: 0xF1
>>            syntax: w  which means: word
>>          category: j:Japanese l:Latin
>>       buffer code: #xC3 #xB1
>>         file code: #xC3 #xB1 (encoded by coding system no-conversion)
>
>> If I'm hopelessly wrong, I'm quite ready to be enlightened (and
>> perhaps the docs will need work).
>
> Indeed that's a bug in C-u C-x =.  It should pay attention to the
> buffer's enable-multibyte-characters and then present #xf1 not as
> a latin-1 char but as a raw-byte.

Well, that makes sense. I'm filing the bug report.

    Juanma

Previous Next

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