public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: rpjday@mindspring.com (Robert P. J. Day)
Cc: szepe@pinerecords.com, linux-kernel@vger.kernel.org
Subject: Re: a few more "make xconfig" inconsistencies
Date: Wed, 1 Jan 2003 14:45:20 +0000 (GMT)	[thread overview]
Message-ID: <200301011445.h01EjK3Q000861@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301010922160.18348-100000@dell> from "Robert P. J. Day" at Jan 01, 2003 09:32:30 AM

> case in point:  under "General setup", there are two (what do
> you call those things?) selectable entries for "PCMCIA/CardBus
> support" and "PCI Hotplug Support".  why not make them selectable
> entries, so i can deselect *all* of PCMCIA/Cardbus support 
> immediately right there?
> 
> as it is, i have to move on to the actual dialog, in which i
> can deselect all of it in one click.  there are other examples:
> "Networking options" -> "Appletalk protocol support".  right now,
> even though it's deselected, the net line reads "Appletalk devices"
> and that dialog *will* come up, albeit deactivated.

The interfaces for the 2.4 and 2.5 xconfig systems are completely
different.

For 2.4, I think it's a very bad idea to not to show the greyed-out
options, because a switch disabling all of them is set.  Having a
switch to disable, for example, all of the power management options is
useful, because they are amoungst other options, and I can just ignore
them and scroll past quickly and easily.

I think it would be a big waste of time if we have to start toggling
options just to see which options are being hidden.

For 2.5, each subcategory can be 'collapsed', so this problem doesn't
really occur.

John.

  reply	other threads:[~2003-01-01 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 14:05 a few more "make xconfig" inconsistencies Robert P. J. Day
2003-01-01 14:16 ` Tomas Szepe
2003-01-01 14:32   ` Robert P. J. Day
2003-01-01 14:45     ` John Bradford [this message]
2003-01-01 14:49       ` Robert P. J. Day
2003-01-01 14:57       ` Robert P. J. Day
2003-01-01 14:51     ` Tomas Szepe
2003-01-01 15:04       ` John Bradford
2003-01-01 15:11         ` Tomas Szepe
2003-01-01 15:24           ` John Bradford
2003-01-01 15:21       ` John Bradford
2003-01-01 15:24         ` Tomas Szepe
2003-01-01 16:08           ` Bill Davidsen

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=200301011445.h01EjK3Q000861@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=szepe@pinerecords.com \
    /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