Re: kbd vs read-key-sequence

[Kenichi Handa]

In article <address@hidden>, Richard Stallman <address@hidden> writes:

>     I think it's a bug.  It surely handles the é the same
>     regardless of the modifiers.  In both cases, it doesn't
>     decode the key event \351 to é.  Windows code ask
>     encoded-kbd-mode to decode it.  And, although
>     Encoded-kbd-mode can decode \351 to é, it can't decode
>     M-\351 to M-é.

> That sounds like a clear bug in encoded-kbd-mode.

Why do you think so?  The task of encoded-kbd-mode is to do
"decode-coding" according to keyboard-coding-system, and
"decode-coding" is to decode a byte sequence into a
character sequence.  But M-\351 is not a byte.

> Can you fix it easily?

It's possible but not easy.

As the other people say, I strongly recommend to add
something like the following text in etc/PROBLEMS.

On Windows, to bind a non-ASCII character with some modifier
to a command, you must specify a raw byte code.  For
instance, if you want to bind meta-a-grave to a command:
  (global-set-key [?\M-\340] ...)
That is for the case of Latin-1 environment where the byte
code of a-grave is \340.

---
Kenichi Handa
address@hidden