Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!douglis@ucbvax.berkeley.edu
From: douglis@ucbvax.berkeley.edu
Newsgroups: comp.windows.x
Subject: Re: WHAT IF ...  Xdefaults weren't such a royal pain to use?
Message-ID: <21979@ucbvax.BERKELEY.EDU>
Date: Sat, 28-Nov-87 16:42:14 EST
Article-I.D.: ucbvax.21979
Posted: Sat Nov 28 16:42:14 1987
Date-Received: Mon, 30-Nov-87 07:03:56 EST
References: <1099@hplabsz.HPL.HP.COM>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: douglis@ginger.berkeley.edu (Fred Douglis)
Organization: U.C. Berkeley
Lines: 25
In-reply-to: mayer@hplabsz.HPL.HP.COM (Niels Mayer)

In article <1099@hplabsz.HPL.HP.COM>, mayer@hplabsz (Niels Mayer) writes:
...
>One's default's should be generated on a "per seat" (or perhaps per
>display) basis rather than on a per host basis.

I'm not sure I agree with this.  While in fact I maintain identical
copies of .Xdefaults on all my machines, there are some times when I
wish I had more flexibility.  The syntax for .Xdefaults will let one
specify different defaults for the same program invoked by different
names, but not the same program on different machines.  Therefore,
when I want to override defaults on a per-machine basis I just have to
specify everything as command-line arguments or make a local copy of
.Xdefaults.  (A solution to the latter problem would be to have
".Xdefaults.local" and then munge the rdisted .Xdefaults each time it
gets copied, but I haven't done that.  In any case, having defaults
handled just by the server could remove any possibility of
host-specific defaults -- unless someone has a good solution to all
this?)
--
===========		===========================	==============
Fred Douglis		douglis@ginger.Berkeley.EDU	ucbvax!douglis
===========		===========================	==============
===========		===========================	==============
Fred Douglis		douglis@ginger.Berkeley.EDU	ucbvax!douglis
===========		===========================	==============