[TF] Bindings and compatability... This may have been covered before..

[naked at iki.fi (N. Kotivuori)]

Kyle Stone wrote:
> I always seem to have a problem when I switch terminal programs
> (xterm, aterm, gnome-terminal, TeraTerm, BSD console, linux console,
> etc) with my keypad navigation bindings working.  What am I doing
> wrong?  The only time I ever seem to get them to work properly is
> when I make a specific one for the $TERM environ and terminal I'm
> using.  It gets tiring making updates for each Terminal/$term only
> to not have them work when a term is updated.  I can't seem to get
> generic bindings to work either...  Such as..  /def -B'KP2' KP_2 =
> /send s with or without the numlock on, VT220, VT100, or ansi..
> This is really aggrevating for me, also.. Anyone have a function off
> hand that will give me the ^[Om' representations for keys to be used
> with -b

You have incorrectly set up terminfo/termcap libraries and/or
incorrectly set up TERM variable. The keys _do_ create different codes
on different terminals.

I would suggest you make sure you are using the latest terminfo from
the ncurses distribution - here's a quicklist of proper terminal types
for your examples:

  xterm-xfree86 - for xterm in XFree86
  rxvt - for aterm
  gnome - for GNOME Terminal
  teraterm - for Teraterm PRO
  cons25 - FreeBSD ANSI console (25 lines)
  linux - Linux console

It's important to notice that all these terminal types are indeed
distinct - and using the wrong one makes it seem like everything
works, when in fact it is indeed incorrect.

Tinyfugue is looking the key binding information from terminfo, hence
if your TERM is set up incorrectly, it will not work. Hence, it's your
responsibility to make sure that the TERM provided actually matches
the capabilities of your terminal. This is even more important with
ncurses software in general and for example 'screen' which translates
the keypresses internally.

-- Naked