mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: John Cowan <cowan@mercury.ccil.org>
Cc: esr@thyrsus.com, james rich <james.rich@m.cc.utah.edu>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.1.3 is available
Date: Tue, 17 Apr 2001 11:14:26 -0500	[thread overview]
Message-ID: <20010417111426.A24230@cadcamlab.org> (raw)
In-Reply-To: <20010416205556.A22960@thyrsus.com> <E14pTOH-0007ex-00@mercury.ccil.org>
In-Reply-To: <E14pTOH-0007ex-00@mercury.ccil.org>; from cowan@mercury.ccil.org on Tue, Apr 17, 2001 at 07:11:25AM -0400


[John Cowan]
> The whole point of CML2 is to make kernel configuration something
> that Aunt Tillie (or a reasonable facsimile thereof) can do, and we
> are all Aunt Tillies from time to time.  That includes differing
> standards of readability,

Come on, that's absolutely a red herring.  There are valid reasons to
want to configure your color schemes, but Aunt Tillie is not one of
them.  Do you seriously believe the novice user will ever futz with a
~/.kernelconfigrc file?  I don't.  Only the (relatively) advanced user
will bother to figure out stuff like that.

If you want your aunt to be able to set her own colors, you basically
have to provide an 'Edit / Preferences...' drop-down or equivalent, and
I think we all know we don't want to go *there*....

> Without counting, I estimate that 50% of the problem (I won't say
> "bug" in this context) reports you have had since 1.0.0 have been
> about colors.

Which basically means Eric and the others have long since shaken out
the serious bugs.  -- Except for the famous 20-second parse, which of
course accounts for the *other* 50% of recent CML2 traffic.

Peter

  parent reply	other threads:[~2001-04-17 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 21:42 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
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         ` Peter Samuelson [this message]
2001-04-17 13:14       ` [kbuild-devel] CML2 1.1.3 is available 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=20010417111426.A24230@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=cowan@mercury.ccil.org \
    --cc=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

all inboxes | Powered by JetHome®