I found the info on the bug tracking system that the home/end key problem was fixed in the latest release.
The xrdb problem was a user error -- have to start a new xterm to test the new resources. I had gotten used to xmodmap working immediately in xterms that were already open. I modified /etc/X11/xdm/Xsetup_0 to add 'xmodmap -e "keycode 22 = BackSpace"'. The backspace key now works properly. Since I can fix the backspace problem in the file xdm is using to start managing the display, I suspect the problem is in some of the system files and not in any of the user setups. If it was a user problem, I would expect the change in Xsetup_0 to be overriden when the user logs in. On Wed, Jul 15, 1998 at 05:17:43PM -0400, Lee Bradshaw wrote: > Hi, > > I installed hamm on a new system about a month ago. Backspace seemed to work > fine on this system. I installed it on a system that had been upgraded from > rex->bo->hamm last week and the backspace key doesn't work properly in X. I > need to type 'xmodmap -e "keycode 22 = BackSpace"' before backspace works > properly. Before using xmodmap, bash gives the following translations: > > <Ctrl-v><bs> ^[[3~ > <Ctrl-v><del> ^[[3~ > <Ctrl-v><Ctrl-h> ^H > > I guess this is redundant, but (also before using xmodmap) xev indicates > that keycode 22 and 107 have the same keysym: > > KeyPress event, serial 18, synthetic NO, window 0x3400001, > root 0x26, subw 0x0, time 2391247581, (120,181), root:(194,272), > state 0x0, keycode 22 (keysym 0xffff, Delete), same_screen YES, > XLookupString gives 1 characters: "" > > KeyPress event, serial 18, synthetic NO, window 0x3400001, > root 0x26, subw 0x0, time 2391250101, (120,181), root:(194,272), > state 0x0, keycode 107 (keysym 0xffff, Delete), same_screen YES, > XLookupString gives 1 characters: "" > > One of my friends at work upgraded two systems from bo to hamm. He has to run > xmodmap on one system but not the other to get backspace to work. > > Also the home and end keys seem to be reversed in X, but work fine on the > console. I tried reversing the strings from the /etc/X11/Xresources in my > .Xresources file and then "xrdb -merge ~/.Xresources", but the keys still > behave incorrectly. > > Any suggestions for solving these problems would be welcome. I can't see > anything wrong with the /etc/X11/Xresources or ~/.Xresources, but I'll be glad > to post these files and more if someone would like to comment. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Alantro Communications [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
