sb> Yes. More NEWS fodder. If your $TERM is "kterm", or begins sb> with the string "kterm" the tty and keyboard coding systems sb> will be unconditionally set to iso-2022-jp after .emacs is sb> read. This is probably a bug. This is definitely a bug. I don't remember if EUC is compatible (ie, auto-recognized) in an ISO-2022-JP environment (I somewhat doubt it however), but SJIS will definitely lose. sb> I wasn't arguing that point. Let's say the user does set sb> iso-8859-2 keyboard and tty coding system in .emacs and is sb> running in a kterm (that's the only way I know of currently to sb> get iso-8859-2 in an xterm-like program). The current code `xterm -fn *-iso8859-2' works for me. sb> will unconditionally change it to iso-2022-jp after .emacs is Arrrrgh. sb> read. There needs to be some way to communicate the fact that sb> the user has done his own initialization and XEmacs/Mule sb> shouldn't override his settings.