Re: Certain keys don't work in emacs in a terminal

[Olive]

Jorge Peixoto de Morais Neto wrote:
> When I use emacs under xterm, pressing <menu>  generates a message that 
> "<print> is undefined"; pressing "C-1" inserts the number 1 as if I had 
> pressed just "1".
> Under a virtual console, the behavior is also wrong, but different.
>
> How can I make emacs work under xterm or under a virtual console as if 
> it was under X?
>
> Thank you.
>
> PS: I am sorry for sending this message again... but there is more than 
> a month and no answer. i won't send any more times.
> --
> Software is like sex: it is better when it is free.

You have to configure your term. For xterm, it work properly if you use 
the following Xresources

XTerm.ttyModes: erase ^?
XTerm.vt100.backarrowKey: false
XTerm.vt100.eightBitInput: false

For the menu key under Xterm, there is a bug in xterm.el (this file load 
specific keys for xterm); change the last line from
(define-key function-key-map "\e[29~" [print])
to
(define-key function-key-map "\e[29~" [home])

This key does not work under the console and in my case the console does 
not recognise it; but you can use Alt-x as normal.

Some distributions put resource remappings some functions keys in Xterm; 
ensure to erase such customization (I assume you know how to deal with 
Xresources, repost if you have problems).

If you want to type non ASCII-characters in your emacs under Xterm, you 
will have to tell emacs which coding system the terminal use; I have in 
my .emacs:

(set-terminal-coding-system 'latin-1)
(set-keyboard-coding-system 'latin-1)

You can even use the mouse wheel under the xterm:

(mouse-wheel-mode 1)

Olive