FW: [TF] Bindings and compatability... This may have been coveredbefore..

[fmcc at clift.o. (<fm...@cl...>]

I use FreeBSD, but have never tried to use the virtual consoles (I run tf
in an xterm...).

I have to say that after reading your two messages, I'm not exactly sure
what you're trying to do.

I can verify that tf works fine on the default 'sco-type' console driver
(cons25 term type), though I've never used the vt220 one.


Is it that you are trying to set up some binding that work the same on the
keypad both under the console driver and in an xterm?  and you dont want
to turn numlock on (which would give '1' both in xterm and in the console
driver) because you want to distinguish the '1' key that is above the 'q'
from the 1 on the keypad?  (the problem being that xterm gives you ^[0F
and the console gives you ^[[F)

You might check an dsee if the 'translations' X resource setting for xterm
would do what you want -- read about 'tranlations' in the xterm man page.

Roughly, you can use translations to turn various key-presses into other
things.

You could put something into your Xresources file and for new xterms, the
kp-1 key would be mapped into whatever you wanted (ie ^[[F - so that it
was the same as the virtual console and could have one set of defs...



A quick look around the net found me some exmaples:

http://www.sunmanagers.org/archives/1992/0241.html
http://216.239.51.100/search?q=cache:g_Lx-96EWs4C:www.ntrnet.net/~jmknoble/old-stuff/xterm-keys.html+xterm+keypad+translations&hl=en&lr=lang_en&ie=UTF-8


This last one
http://www.ibb.net/~anne/keyboard.html
gives a general overview of all the different key-mapping problems unix
boxes have under a variety of software, and gives some good general advice
on how to unify things.

Alternatively, you could make your macro set your bindings based on the
term type of the terminal you were using.

/setenv TERM

will print out the termial type and you could use that to tell wether to
set your vars one way or the other?  Make sense?  You would of course have
to have a block of code in for each type of terminal you were using, and
perhaps a 'default' fall-back setting, but that is better than having to
set it by hand.

Fred