Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bellcore!jello!aw
From: aw@jello.bae.bellcore.com (Andrew Wason)
Newsgroups: comp.windows.x
Subject: Re: How do I remap the keyboard?
Message-ID: <1991Apr13.031209.11423@bellcore.bellcore.com>
Date: 13 Apr 91 03:12:09 GMT
References: <21867@shlump.nac.dec.com> <1991Apr9.172338.10501@medicus.com> <22036@shlump.nac.dec.com>
Sender: usenet@bellcore.bellcore.com (Poster of News)
Reply-To: aw@bae.bellcore.com
Organization: Bell Communications Research
Lines: 47

In article <22036@shlump.nac.dec.com>, lan_csse@netrix.nac.dec.com (CSSE LAN Test Account) writes:
>Not yet; I've tried a couple of variants, such as:
>*xterm*translations: #override <Key>F13: string("You touched F13") \n\
>				   <Key>F14: string("You touched F14")
>
>After adding this to .Xdefaults and saving it, I start up an xterm, in which 
> [...]
>This is the old "\e[26~" that was there before; nothing whatsoever has been
>changed.
> [...]
>What am I doing wrong?  Is there something I need to do other than write
>a new .Xdefaults?  Is it perhaps getting a cached version from the server
>instead of reading it from $HOME/.Xdefaults?  Am I wasting my time?

Are you sure your xterm is named "xterm"?  Try using XTerm*translations
(class instead of name) and see if that works.

>Also, it'd be nice if I didn't have to edit .Xdefaults to do this.  After
>all, there are likely to be different applications running inside different
>windows; they may well need to different mappings.  One of our applications
>wants to talk to a DOS system, and it should send the function-key codes
>that the IBM keyboard sends, else the DOS programs won't recognize them.
>Other applications are talking to other systems remotely, and they need to
>respond to the F* keys by sending whatever the remote system expects.  


You can run each xterm with a different name and specify resources
specific to each name.
e.g.

  xterm -name larry&
  xterm -name curly&

  larry*translations: ...
  curly*translations: ...

Even better, xterm supports dynamically defining new translation
tables.  You can set up default translations which allow you to
switch between different tables at runtime.  See the man page.

Andrew

_______________________________________________________________________________

Andrew Wason                                       Bell Communications Research
aw@bae.bellcore.com                                Piscataway, NJ
bellcore!bae!aw