×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Phillip.Watts@xxxxxxxxx wrote:
I am afraid I don't get it. I am supposed to put all the keymapping
for xt5250 in ~/.Xdefaults but I have no idea what to do.
In order to define non US PC keyboard I need to define scancodes
as they do in /usr/share/keymaps/us.kmap.gz.
Could someone send me a sample Xdefaults which defines scancodes
and maps them to actions?
For instance, I wish to use right-ctrl( scan code 97) as ENTER
and enter(scan code 28) as field exit.
Is there any sort of writeup for the format of Xdefaults?
Xdefaults has the same format as the XTerm file installed in
/usr/local/share/tn5250. There is documentation on Xdefaults in
general available on the XFree website, but that probably isn't what
you're looking for. The part you're interested in is the Translations
string (xt5250*VT100.Translations) which describes how keys relate to
values passed to xterm. The tn5250-HOWTO contains info on how to make
the map. From the HOWTO, in order to make enter on the 10-key pad be
field exit put the following in your ~/.Xdefaults:
xt5250*VT100.Translations: #override\n\
<Key>KP_Enter: string("\033X")
Also look in the appendix of the HOWTO for complete examples.
The HOWTO is located at:
http://www.chowhouse.com/~james/tn5250-HOWTO.pdf
If you have read it and it still doesn't make sense let me know. I've
tried to make it as simple as possible, but perhaps the keymap section
isn't very clear, or perhaps it could use more illustrative examples.
James Rich
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.