keyboard remapping for Mandrake 7.0

[glennl]

Hi,<br>
<br>
I am having problems getting the up and down arrow keys to work under Xterm. I press the up, down, left and right keys and [A through [D appear respectively in my application. My software app requires &lt;Ctrl&gt; K, &lt;Ctrl&gt; J, for up and down etc. What files do I need to edit to modify the function of these keys and where are they located. I also need to know where my personal login script would be located to set my datapath, path, termcap settings, etc.<br>
<br>
Any help would be greatly appreciated. Thanks in advance.<br>
<br>
<br>

 

[AndyBo]

Which software app are you running? The cursor key outputs you've described are correct for an xterm...<br>
<br>
The app should really be referring to termcap and/or terminfo to get the definitions of the cursor keys for your current terminal emulation setting. As it sounds like it isn't, the best thing for you to do would be to take a look at the man page for &quot;xmodmap&quot;.<br>
<br>
&quot;xmodmap&quot; lets you change the keyboard mappings that are used by X clients.<br>
<br>
I've not used it, but I hope it's a pointer in the right direction for you. It might be an idea to tray and amend, or get amended, the app that you are using...<br>
<br>
HTH.

 

[glennl]

AndyBo,<br>
<br>
Thanks for answering so quickly. The application I am running runs fine on SCO OpenServer 5.0.5 which is our current O/S. We can get the keys to work well in SCO by editing the termcap file. When we edit the termcap file for Mandrake 7.0 the changes do not take effect. In fact no environmental variables, such as PATH, TERM, etc take effect. However we just noticed that if we change to csh instead of bash shell, infocmp and tic do affect the terminal settings. Editing inputrc and bashrc have no effect on the terminal in bash shell. Let me know if you have any more ideas.<br>
<br>
Thanks<br>
<br>

 

[AndyBo]

No problem, Glenn.<br>
<br>
Originally, I was going to suggest looking at termcap and terminfo, but avoided doing so because it can start to get a bit involved. Looks like you've already tried it <br>
<br>
I can't think of anything else to try. Updating termcap or terminfo should work... I'll have a think, and let you know if I come up with anything.