Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: mouse@larry.mcrcim.mcgill.EDU
Newsgroups: comp.windows.x
Subject: Re:  xmodmap question (maybe dumb :-)
Message-ID: <9101060429.AA18755@Larry.McRCIM.McGill.EDU>
Date: 6 Jan 91 04:29:47 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 42

> I have tried to map the up, down, left and right cursor key to new
> Control keys.

> My .xmodmaprc is:

> keycode 87 = Control_B
> keycode 91 = Control_P
> keycode 92 = Control_N
> keycode 91 = Control_F

> Unfortunately xmodmap displays the following error messages:

> xmodmap:  .Xmodmap:0:  bad keysym name 'Control_B' in keysym list
> xmodmap:  .Xmodmap:0:  bad keycode keysym list
[etc]

There is no such key as Control_B.  Control-B is a combination, typed
using two keys (Control and B); XLookupString turns a down event for a
B key, when the Control modifier is active, into a ^B character.

xmodmap allows you to rearrange keys on your keyboard; it does not
allow you to reassign keys arbitrarily.

Depending on what you want, it may be possible to use a different
mechanism.  Many Xt clients (xterm among them) have a Translations
resource which allows you to reassign key meanings for that client;
this would allow you to do what you appear to want to do - but only for
clients that understand the resource.

I am hoping R5 addresses the common wish to "assign a string to a key"
in a client-independent manner.  If it doesn't, I will probably try to
hack something into Xlib to deal with it.

> That is not dead, which can eternal lie.
> Yet with strange aeons, even death may die.

I know that quote, I'm sure of it.  Lloyd Alexander?

					der Mouse

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