bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1935: marked as done (describe-char does not show raw bytes as such


From: Emacs bug Tracking System
Subject: bug#1935: marked as done (describe-char does not show raw bytes as such)
Date: Tue, 20 Jan 2009 06:15:02 +0000

Your message dated Tue, 20 Jan 2009 15:08:33 +0900
with message-id <E1LP9mr-0007Br-L0@etlken.m17n.org>
and subject line Re: [EMACS] categories in output of `describe-char'
has caused the Emacs bug report #1935,
regarding describe-char does not show raw bytes as such
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
1935: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1935
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
--- Begin Message --- 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@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



--- End Message ---
--- Begin Message --- Subject: Re: [EMACS] categories in output of `describe-char' Date: Tue, 20 Jan 2009 15:08:33 +0900 User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
In article <f7ccd24b0901190754m1a319ad2m97a9d0072a29da40@mail.gmail.com>, 
Juanma Barranquero <lekktu@gmail.com> writes:

> On Mon, Jan 19, 2009 at 12:12, Juanma Barranquero <lekktu@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@m17n.org


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]