--- 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 ---