Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!nntpd.lkg.dec.com!netrix.nac.dec.com!lan_csse From: lan_csse@netrix.nac.dec.com (CSSE LAN Test Account) Newsgroups: comp.windows.x Subject: Re: How do I remap the keyboard? Message-ID: <22527@shlump.lkg.dec.com> Date: 8 May 91 16:08:31 GMT References: <24228@well.sf.ca.us> <22171@shlump.nac.dec.com> Sender: news@shlump.lkg.dec.com Organization: Digital Equipment Lines: 47 In article clive@x.co.uk (Clive D.W. Feather) writes: |In article <22171@shlump.nac.dec.com> lan_csse@netrix.nac.dec.com (CSSE LAN Test Account) writes: |> ... So xterm doesn't open .Xdefaults at all. A bit more |> experimenting verified that if I kill X off and restart it, xterm then |> uses the contents of .Xdefaults. Thus .Xdefaults is cached inside the |> X server, and xterm gets the info from there. This also explains why |> xterm is to incredibly slow when started across a SLIP link; the entire |> .Xdefaults file is stuffed across the link for every xterm. A line |> monitor verifies this; you can see the data flow by. Sigh. | |This behaviour is caused because you are running xrdb(1) from your |start-up file. No, I'm not; grep can't find the string "rdb" in any $HOME/.* file. It also fails to find it in /etc/ttys (where the server is started on this Ultrix system). It also can't be found in any file in /usr/lib/X11 or any subdirectory. If there is a call of xrdb somewhere, it is hidden so well that I've been unable to find it. Perhaps when I go home I'll leave behind a find that scans every file in all the disks... | ... This loads a copy of .Xdefaults on the server, in such a |way that XOpenDisplay (the Xlib function) will see it and copy it into |the application data space when opening the display. Xterm then sees that |this has been done, and uses it instead of .Xdefaults. There are good |reasons for this feature which I won't go into, but if you're using |SLIP, then you want to disable it. Just remove the xrdb command from you |start-up file. OK, so any hints as to how to find the sucker so I can disable it? |Try: | | Help : string("You are an")string(0x0d)string(0x0a)string(Idiot!) Actuall, I prefer: Help : string(0x0D)\ string(0x0D)string(0x0A)\ string("You are beyond help!")\ string(0x0d)string(0x0A)\ string(0x0d)string(0x0A) Thanks to everyone for the examples. We actually have some DOS applications running quite well from inside an xterm now. The major remaining problem is deciphering why we sometimes get '3' instead of '|' from pcanywhere, but this is probably not anything that xterm can help us with. Now to write up a sensible summary...