Yoshiaki Kasahara <kasahara(a)nc.kyushu-u.ac.jp> writes:
Several months ago I reported that I couldn't input 'C-o'
at all in
XEmacs running in tty. Today I noticed some additional behavior
related to that.
I investigated it briefly. I think I found a workaround and
probable cause of the problem.
The version I tested was (emacs-version)
"XEmacs 21.5 (beta14) \"cassava\" (+CVS-20030708) [Lucid]
(i686-pc-linux, Mule) of Tue Jul 15 2003 on mito"
When I'm using 'TERM=xterm' or 'TERM=vt100', if I
immediately type
'ESC' or meta+something just after XEmacs starts, I can use 'C-o' as
usual. On the other hand, if I type other keys such as 'C-n', I
cannot input 'C-o' at all (XEmacs ignores it). Additionally, hitting
meta+something is only interpreted as 'ESC'. The minibuffer only
shows 'ESC -' when I hit 'M-x'.
What's the return value of (keyboard-coding-system)? I
tested with two terminals, konsole and xterm. C-o works on
konsole but not on xterm. The value of
(keyboard-coding-system) is raw-text on konsole and
undecided-unix on xterm. Evaluating
(set-keyboard-coding-system 'binary) on xterm version makes
C-o work again. If I evalute (set-keyboard-coding-system
'undecided-unix) then C-o stops working. The strange thing
is that C-o works on konsole even if keyboard-coding-system
is undecided-unix. My guess is that something is wrong with
coding system detection stuff. I have no idea why it works
on knosole without problem.
I suggest users of console XEmacs 21.5 to put
(set-keyboard-coding-system 'binary) in .xemacs/init.el to
workaround the problem until it is fixed correctly. I have
no time nor intention to dive into the detail of new coding
system stuff at the moment.
When I'm using 'TERM=kterm', this method doesn't work
from the
beginning. So I can't input 'C-o' at all and the meta key doesn't
work correctly.
There's a hack in lisp/mule/mule-tty-init.el that sets
keyboard-coding-system and output-coding-system to euc-jp
when terminal is kterm. You may try the same workaround. I
can't test C-o on kterm as input method eats that key,
though.
--
Yoshiki Hayashi