public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: james rich <james.rich@m.cc.utah.edu>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] CML2 1.1.3 is available
Date: Mon, 16 Apr 2001 20:55:56 -0400	[thread overview]
Message-ID: <20010416205556.A22960@thyrsus.com> (raw)
In-Reply-To: <3ADB69BF.7040305@reutershealth.com> <Pine.GSO.4.05.10104161622110.17365-100000@pipt.oz.cc.utah.edu>
In-Reply-To: <Pine.GSO.4.05.10104161622110.17365-100000@pipt.oz.cc.utah.edu>; from james.rich@m.cc.utah.edu on Mon, Apr 16, 2001 at 04:28:18PM -0600

james rich <james.rich@m.cc.utah.edu>:
> > Instead, read the colors from the .Xdefaults system.
> 
> Yes, truly this should be done.  Sensible defaults should be used (and I
> think we may be at that point) and then use .Xdefaults (.Xresources or
> whatever) to allow site overrides.  And I really do think .Xdefaults and
> not .xconfigrc or something.  I've already got enough .files and I like
> the syntax of .Xdefaults.

That way lies featuritis, IMO.

If there were already a library in ths stock Python distribution to digest
.Xdefaults files I might consider this.  Perhaps I'll write one.  But I'm
not going to bulk up the CML2 code with this marginal feature.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The conclusion is thus inescapable that the history, concept, and 
wording of the second amendment to the Constitution of the United 
States, as well as its interpretation by every major commentator and 
court in the first half-century after its ratification, indicates 
that what is protected is an individual right of a private citizen 
to own and carry firearms in a peaceful manner.
         -- Report of the Subcommittee On The Constitution of the Committee On 
            The Judiciary, United States Senate, 97th Congress, second session 
            (February, 1982), SuDoc# Y4.J 89/2: Ar 5/5

  reply	other threads:[~2001-04-17  0:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 21:42 CML2 1.1.3 is available Eric S. Raymond
2001-04-16 21:53 ` [kbuild-devel] " John Cowan
2001-04-16 22:28   ` james rich
2001-04-17  0:55     ` Eric S. Raymond [this message]
2001-04-17  1:28       ` Peter Samuelson
2001-04-17  3:20         ` Eric S. Raymond
2001-04-17  8:06           ` Andrew Pimlott
2001-04-17 10:25           ` Olaf Titz
2001-04-17 11:11       ` [kbuild-devel] " John Cowan
2001-04-17 14:38         ` Eric S. Raymond
2001-04-17 15:23           ` CMLConfigurator skins (was: CML2 1.1.3 is available) John Cowan
2001-04-17 16:14         ` CML2 1.1.3 is available Peter Samuelson
2001-04-17 13:14       ` [kbuild-devel] " Mike A. Harris
2001-04-19 23:20       ` Adam Sampson
2001-04-22  0:03         ` Albert D. Cahalan
2001-04-16 22:00 ` Steven Cole
2001-04-16 22:06   ` Eric S. Raymond
2001-04-16 22:26     ` Steven Cole
2001-04-17  7:15 ` Marko Kreen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010416205556.A22960@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=james.rich@m.cc.utah.edu \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox