Re: raw-text coding system confuses input method

[Kenichi Handa]

In article <address@hidden>, Stefan Daschek <address@hidden> writes:
> Hmm. I see that this is a problem but how about if Emacs would give a
> warning message like when you try to save a file without a suitable
> coding system? 

Emacs already do that for a multibyte buffer.  But, an
unibyte buffer (that is your case) is written as is (with
eol conversion if necessary).

>>  For that matter, what is the real-world problem behind the sequence of
>>  events that you reported?  That is, why would one need to insert a
>>  unibyte character into a buffer and then add multibyte characters to
>>  that same buffer?

Even in a unibyte buffer, you can use quail input method in
some situation.  For instance, if you are in Latin-1
lang. env., and you use latin-1-prefix in a unibyte buffer.
In that case, all multibyte characters input by the input
method are converted to the corresponding unibyte
characters.

> My .emacs file contained some \205 characters (not sure why, I got rid
> of them in the meantime), and I was trying to input a horizontal
> ellipsis using rfc1345 input method. It then took me quite a long time
> to figure out why it didn't work as expected (I had to look up the
> correct mnemonic for horizontal ellipsis to make sure I didn't make a
> mistake and so on). I think it would have been really helpful if Emacs
> had displayed a warning message when I tried to insert a multibyte
> character.

I've just add such a feature, i.e., if you are going to
insert a multibyte character in a unibyte buffer via quail,
and that multibyte character is not what supported in your
language environment, quail shows a proper error message.

---
Ken'ichi HANDA
address@hidden