jac@eros.berkeley.edu (Gordon Jacobs) (08/25/89)
I just received a DECstation 3100 and I am running the uwm window manager. (either manually or under the dxsession manager) When I press the "Compose Character" key, which is my Meta key to move windows around, etc as described in my uwmrc file, the LED labelled "Compose" comes on adn stays on. If I then move the mouse into another window and begin typing, the first several characters are lost, a "beep" occurrs, the "Compose" LED goes out and then everything is normal again (until I use the Meta key). We have other 3100s around and they don't seem to do this. Running xmodmap reveals that the key is called "Multi_key" and it is mapped to "mod1" modifier. Does anyone know what is going on here? It seems like the Compose key has some feature intentionally that is getting in the way of normal operation of uwm. Any help appreciated... (BTW, swapping keyboards did not help) thanks Gordie Jacobs
tarsa@abyss.ZK3.DEC.COM (Greg Tarsa) (08/25/89)
xmodmap -e 'keycode 0xb1 = Alt_L'
FYI, you can put the angle brackets back over the period and comma keys
using the following xmodmap lines:
xmodmap -e 'keycode 0xe8 = comma less'
xmodmap -e 'keycode 0xed = period greater'
Enjoy,
Greg
Tarsa Software Consulting
--------------------------------
33 Seabee Street
Bedford, NH 03102 tarsa@elijah.mv.com
(603)668-8349 {decuac,decvax}!elijah!tarsaklee@chico.pa.dec.com (Ken Lee) (08/26/89)
In article <16536@pasteur.Berkeley.EDU>, jac@eros.berkeley.edu (Gordon Jacobs) writes: > I just received a DECstation 3100 and I am running > the uwm window manager. (either manually or under > the dxsession manager) When I press the "Compose Character" > key, which is my Meta key to move windows around, etc as > described in my uwmrc file, the LED labelled "Compose" > comes on adn stays on. If I then move the mouse into another > window and begin typing, the first several characters are > lost, a "beep" occurrs, the "Compose" LED goes out and then > everything is normal again (until I use the Meta key). I'm not really familiar with uwm, but could this be a problem with uwm and keyboard focus? uwm is probably doing a grab on the compose key. If you release the key, move the mouse cursor to another window, and start typing, uwm must release the grab and assign focus to the new window. If you start typing before uwm can do all that, the keystrokes won't go where you're expecting. Does the problem still occur if you wait a few seconds before typing? How about if you use a different character as your uwm control? Or a different window manager, especially a click-to-type one like dxwm? Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@decwrl.dec.com uucp: uunet!decwrl!klee