Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  Keybinding problem on OWR2
Message-ID: <9011091641.AA29114@Larry.McRCIM.McGill.EDU>
Date: 9 Nov 90 16:41:39 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 38

> I'm having a problem getting my keybinding right on OWR2 on a SS1.  I
> want the backspace and delete key to both generate a delete under all
> circumstances.

> Initially xmodmap -pk tells me:
> 	 50         0xff08 (BackSpace)
> then after I do a 
> 	xmodmap -e "keysym  BackSpace = Delete"
> it becomes:
> 	 50         0xffff (Delete)

That looks fine, yes.

> Which looks correct.  However, when I run a terminal oriented program
> I get ^H when I hit the backspace key.

Yow.

One possibility is that there's more than one keycode that's set to
BackSpace, and you changed the wrong one.  Look through xmodmap -pk
output for other BackSpace keysyms.  If that's not it, something
strange is wrong.  Does xmodmap -pk still report that it's a Delete?
If so, the program is doing something seriously wrong; it must be
looking at the keycodes, which it is not supposed to do.  Check with
xev (see below) and make sure that it really is set to Delete....

> By the way is there a program around that prints out keycodes while
> you press keys?

xev will do this.  Run xev, give it focus (put the mouse in it,
typically) and type at it.  On xev's standard output you will get
(among many other things) descriptions of the keys pressed in terms of
keycodes, keysyms, and strings returned by XLookupString().

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu