02-09-2004 10:57 PM
key combinations. Having used xmodmap -pk I see that the 3rd definition of a key
is not defined. I can define it by hand which works fine for hpterm and xterm,
NOT for dtterm.
firstly: what should I do to get this working from the start of a users session?
secondly: what should I do to get it working in dtterm?
The system is accessed through CDE at the HP and Cygwin at the clientÂ´s side.
02-09-2004 11:22 PM
To get the users key map set up at start you just create a standard keymap file which you call $HOME/.xmodmaprc. You then put the xmodmap command in the users .profile.
If it is a system wide problem you can put the xmodmap command in /etc/profile, put your keymap file somewhere central like /etc/xmodmaprc and use /etc/xmodmaprc as an argument to your "xmodmap" command.
I do not know how you achieve the same thing with dtterm but I think you might have to use the -xrm argument and a resource string of some kind. The only X resources I know about for dtterm are here (near the bottom of the page)
02-11-2004 12:14 AM
Prior to running dtterm:
# export XKB_DISABLE=1
to see if this addresses the problem.
The main difference between hpterm and dtterm in this area is that hpterm is based on X11R5 which never supported XKB and dtterm is based on X11R6 which did. Setting the environment variable forces dtterm down the 'old' path and may offer some relief.
Other symptoms of the XKB failure include the inability of the shift lock to operate properly.
02-11-2004 09:59 PM
more information on how to use it when logging on via X/ CDE.
I have put XKB_DISABLE in the /etc/profile file, but it doesn't make any difference to dtterm.
02-11-2004 10:11 PM
02-12-2004 07:09 PM
/etc/profile. It works if it is executed by hand.
I guess it should be executed as soon as a X-application is started.
02-16-2004 07:36 PM
I tried to put the xmodmap command in .dtprofile.
It helps to define the keys for hpterm and xterm. The altGr key is not
working for dtterm however, nor for the X-application of sas we use.
Please tell me what to do
02-16-2004 07:53 PM
This is quite an interesting link. It would seem dtterm, being Motif handles things slightly different. It seems you might need to put an override in the Xdefaults file. If your appliaction is based on Motif, it will have the same problrm as dtterm. Anyway, have a look and let us know if you need any help with it. At least, let us know how you get on!
02-25-2004 04:07 AM
I have the same problem, ALT-GR not working, not with dtterm, but with plain xterm.
I am starting an xterm remote on an HP machine from a linux box, via ssh or rsh, it does not matter and have the display on my linux box.
Neither @ nor | works. I checked the xmodmap output and the mod3 key, that used to be the define for alt-gr is not set any more. And I cannot set it to ALT_R, because xmodmap does not know the name ALT_R.
Looking at the output of xev I found that the ALT-GR key is now ISO_Level3_Shift (Keycode 0x71). Setting mod3 to ISO_Level3_Shift did not help, nor did the additional clear of mod5, which was orginally to ISO_Level3_Shift.
Does anybody have any additional idea what else to try?
Thanks in advance
03-05-2004 03:14 AM
I install the xkeycaps Tool that give a graphic view of keybord; the Altgr key is right interpreted in that case. But definitively the dttem is not understanding the key.
I do a try with an other Xserver live Omni-X and the altgr key is responding.
I'am affraid that the problem comme from cygwin/xfree server.
One thing is that i got some fonts error when running dtterm with '-dt-interface' error.
does the problem could be from font setting on cygwin/xfree that are not compatible with HP request.