Re: kbd vs read-key-sequence

[Stefan Monnier]

>> Looks like a bug in our w32 code, where we somehow fail to decode the chars
>> before returning them from read-key-sequence.

> I honestly cannot say whether it is a bug in the w32 code, or the
> consequence of the complexity of input decoding (with
> keyboard-translate-table, translation-table-for-input,
> function-key-map, key-translation-map, coding systems and whatnot).

> In any case:

> ;; Kubuntu 6.10
> read-char / read-event => 2234
> (aref translation-table-for-input 2234) => 2234
> (lookup-key key-translation-map [186]) => nil

> ;; Windows XP SP2
> read-char / read-event => 186
> (aref translation-table-for-input 2234) => nil
> (lookup-key key-translation-map [186]) => encoded-kb-self-insert-ccl

[ BTW, please always specify whether this is in "console mode" or not,
because the way keys are translated can be different in each case. ]

Hmm... so w32 does decoding using keyboard-coding-system (aka
encoded-kb)?

But then why does read-key-sequence return 186 as well?  read-key-sequence
should be using key-translation-map and hence turn it into 2234.

What does keyboard-coding-system say?


        Stefan