Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!hplabs!hplabsz!mayer From: mayer@hplabsz.UUCP Newsgroups: comp.windows.x Subject: WHAT IF ... Xdefaults weren't such a royal pain to use? Message-ID: <1099@hplabsz.HPL.HP.COM> Date: Tue, 24-Nov-87 20:30:43 EST Article-I.D.: hplabsz.1099 Posted: Tue Nov 24 20:30:43 1987 Date-Received: Sun, 29-Nov-87 04:52:36 EST Reply-To: mayer@hplabsz.UUCP (Niels Mayer) Organization: Hewlett-Packard Laboratories Lines: 15 Is there a decent reason why .Xdefaults isn't read in by the X server and all subsequent calls to XGetDefault generate queries to the server? One's default's should be generated on a "per seat" (or perhaps per display) basis rather than on a per host basis. It looks like X11 might let me "override" the traditional methods of getting ~/.Xdefaults by letting me put all the Xdefaults as properties of, say, the root window. I would leave the definition of XGetDefault the same but change the implementation to query the server for the data. Is anybody doing this already? Can you think of a good reason why I shouldn't? -- Niels Mayer.