On Wed, Feb 23, 2000 at 10:06:30PM +0200, Marius Gedminas wrote:
> You should try hacking terminfo instead. Use
> $ infocmp $TERM
> and look at khome, kend, kpp and knp. They should match the sequences
> your term is generating for Home, End, PgUp and PgDn respectively.
I just solved this for xterm on my RH 6.1 Linux box, by adding
the following to the vt100 entry:
khome=\EOH, kend=\EOF, knp=\E[6~, kpp=\E[5~,
Those who do not have root permission or a cooperative sysadmin
can add the following to their .muttrc as a work around:
bind generic '<esc>[5~' previous-page # Page Up
bind generic '<esc>[6~' next-page # Page Down
bind generic '<esc>OH' first-entry # Home
bind generic '<esc>OF' last-entry # End
(In either case you must substitutes the actually codes
that your term emulator is generating)
> (keystrings is a small program whose sole purpose in life is to display
> nicely formatted character sequences. I hacked it from examples in
> libc.inf).
Another way to see the codes is to start up emacs in the xterm (use
the -nw flag so it does not start up in its own window). Go to the
scratch buffer and type ^Q followed by whatever key you want to see.
The xterm on linux was kind enough pass along the Home, End, PgUp and PgDn
keys to emacs so I could view them. The xterm on Solaris was greedy,
grabbing them for itself, so this didn't work.
- Dan
