Re: bug: set-terminal-coding-system doesn't work?
"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes:
steve> I can't reproduce this on DEC OSF with dtterm, and I
am
steve> having trouble getting a clean build of 21.2 on Solaris.
steve> Which terminal emulator are you using?
I'm using shelltool within the OpenWindows environment.
Because I can enter Japanese text using vi in shelltool,
I don't think this is a shelltool problem.
It doesn't matter of terminal emulator but input method, doesn't it?
I think Steve is using Wnn or Canna within egg-its world, but
Kurosaka-san is using ATOK, kinput2 or something like that; it is an
input method resides in outside of lisp.
I just confirmed it with
* run kinput2 and kterm
* run both "xemacs -nw" and "xemacs -nw -vanilla" in kterm
In both cases of "xemacs ...", when I type some Japanese word using
kinput2 and going to put those string in xemacs, xemacs accepts those
string as some sequence of command from keyboard, not string.
For example, those messages are shown in mini-buffer:
- M-" not defined.
- End of buffer
- Shell command on region:
- No M-x tags-search or M-x tags-query-replace in progress.
Of course, the X input method works well when I use XEmacs in X.