André Dahlqvist <[EMAIL PROTECTED]> writes:
>This actually varies a bit depending on which character I try to insert,
>if I try to write é the cursor jumps a few positions as if I had typed a
>tab. When I insert ö it beeps, and when inserting å or ä abolutely
>nothing happens. Remember that all of these things work flavlessly if I
>run emacs on the console or as a stand alone X app, and only fails when
>I run it inside an xterm or rxvt. But the xterm itself accepts these
Try adding the following to your ~/.emacs:
;; For entering 8-bit characters without C-q from an xterm
(set-input-mode (nth 0 (current-input-mode))
(nth 1 (current-input-mode))
0)
Why? A terminal normally sends the same "code" for eight-bit
characters and Meta-keys, so, for instance, ä and M-d give the same
byte to Emacs (the ASCII code for d with the 8th bit set), and Emacs
can't know which one you pressed. By default, Emacs guesses that you
wanted M-d, and the elisp code above changes that default.
Thus, a side effect of the code above is that Meta doesn't work in
Emacs inside an xterm (or similar); use ESC instead (ESC d is the same
as M-d for Emacs).
There is a way to get both Meta and eight-bit characters to work in an
xterm: Start xterm with "xterm -xrm '*eightBitInput: false'" or put
"XTerm*eightBitInput: false" in your ~/.Xresources, and use the code
above in your ~/.emacs. But this might possibly break some other
programs that use Meta inside an xterm, I'm not sure. (It makes xterm
send ESC d when you press M-d, so then ESC d and M-d are
indistinguishable. This doesn't matter for Emacs, and I can't think of
a program where it would matter, but there might be some.)
--
-=- Rjs -=- [EMAIL PROTECTED]
