home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!uakari.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!carson.u.washington.edu!donn
- From: donn@carson.u.washington.edu (Donn Cave)
- Newsgroups: comp.windows.x
- Subject: Re: xdm and key mappings
- Message-ID: <1992Jul29.155257.9065@u.washington.edu>
- Date: 29 Jul 92 15:52:57 GMT
- References: <1992Jul24.164719.3607@cs.tulane.edu> <9207281856.AA25049@alex.lcs.mit.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington
- Lines: 19
-
- gildea@expo.lcs.mit.EDU (Stephen Gildea) writes:
-
- | When he finishes with his login session, the keys still remain mapped to
- | DVORAK.
-
- | This implies that the X server is not being reset between sessions.
- | It is supposed to be. Users may make many changes to their server,
- | the root background and resource database being two other common
- | examples. When the server resets, all this is undone. Either your X
- | server has a bug, or you are not setting up xdm correctly.
-
- This is optional with some servers, however. Some X terminals, for example,
- come with a "Retain X Settings" option, which if enabled will defeat the
- above-described behavior. Which saves a lot of time hashing font paths,
- among other things. In this case, it's not a bug - it really is a feature,
- as long as it's properly used.
-
- Donn Cave, University Computing Services, University of Washington
- donn@cac.washington.edu
-