Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.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: <22639@shlump.lkg.dec.com> Date: 13 May 91 18:48:45 GMT References: <22527@shlump.lkg.dec.com> <1991May9.005015.26856@parc.xerox.com> Sender: news@shlump.lkg.dec.com Organization: Digital Equipment Lines: 36 In article <1991May9.005015.26856@parc.xerox.com> kent@Xerox.com (Chris Kent) writes: > Since you're posting from a DEC site, and since I seem to remember that > netrix is an Ultrix machine, I bet you're running the DEC session manager. > One of the first things that it does when it starts up is run xrdb on your > .Xdefaults. You lose; pay up! (;-) True, netrix is an Ultrix machine, but this is an rlogin session from another machine. This machine is also Ultrix, but I'm running mwm (Motif), not dxwm. My other machine is running uwm, and I'm having fun trying to get mwm to match the feechurz (and user-friendliness) of uwm. There's not a dxwm in sight (we all hate it :-). >That's why you couldn't find it anywhere else. So why do uwm and mwm do it? Can I get them to stop? Also, what I'd really like to do is: We have two machines that have just set up a new SLIP link. Their owners started up X however they felt like, and they likely don't even understand much about how it works. One of them wants to start up xterm on machine $A with the DISPLAY set to $B:0 across the SLIP link. How can I tell the xterm to ignore *whatever* the remote X server tells it, and read a local resources file? The intent is to eliminate the huge pile of resource messages that get stuffed through the 9600-bps pinhole, so they can perhaps start in 10-20 seconds rather that the 1-2 minutes that it now takes. I can easily link xterm to other names or embed it within a script; packaging it for users is no problem. But what to put in the package isn't at all obvious. More generally, we have an assortment of applications that are essentially unusable across a slow network, because the startup time is so slow that the users have forgotten what they were doing by the time the window pops up. SLIP isn't the only problem; we have some multi-gatewayed (T1) links that are even slower than 9600-bps SLIP, and it'd be nice if they could be made minimally usable. We've sort of assumed that it was hopeless, and that our graphics applications (even the most trivial) are unusable across them. If we're wrong, we'd love to be told just exactly how wrong we are, possibly with some demos of our wrongheadedness...