|
Scott, > Okay... The contents of the XTerm file have always worked for me out of > the box on both FreeBSD and RedHat. I've never tried Gentoo, but I'm > not sure why it'd be different. And they worked for me on RedHat9. The only thing special about Gentoo is that you compile it specifically for the machine it is going to run on - the processor and graphics card, mostly. It takes forever but the end result is a highly optimized implementation. > manually manipulate that database as well. If you want to see if your > .Xdefaults file has loaded successfully, you can do: > xrdb -query I ran xrdb -query and everything appears to be correct, at least according to the contents of my .Xdefaults file. > So, if your keys aren't working, either the overrides aren't being placed > in the database, or the xterm isn't acting on them, or the wrong string > is being sent to tn5250. I'll assume this is all related: when I run tn5250 I have the exact same problems as xt5250. > I hope this helps you drill down and see what the problem is. You might > also consider changing the "xt5250*" string at the start of your > .Xdefaults file to be "xterm*" and see if you can get your xterm to send > strings without tn5250. This might help you to see what steps you need to > take to get strings sending properly. If this works, what does it tell me? > An alternative to all of this is to try the gtk-5250 (gnome-5250) terminal > front-end for tn5250. That version reads the raw keyboard scancodes > instead of letting xterm remap things, which may work better, who knows? This is honestly where I get confused about Linux (remember I'm fairly new) - does it matter that I'm running KDE? Will Gnome still work? I was very satisfied with xt5250 on RedHat and I'd like to avoid a terminal solution if I can. Thanks again, Joel http://www.rpgnext.com
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.