From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: John Bradford <john@grabjohn.com>
Cc: rpjday@mindspring.com, linux-kernel@vger.kernel.org
Subject: Re: some kernel config menu suggested tweaks
Date: Thu, 24 Jul 2003 21:53:22 +0200 [thread overview]
Message-ID: <20030724195322.GA8194@vana.vc.cvut.cz> (raw)
In-Reply-To: <200307241910.h6OJAWnm000706@81-2-122-30.bradfords.org.uk>
On Thu, Jul 24, 2003 at 08:10:32PM +0100, John Bradford wrote:
>
> The filesystem menu, for example, I could previously just skip down in
> make menuconfig, selecting and deselecting what I wanted. Now, I have
> to go in and out, and in and out, just to see what's selected and
> what's not. Sure, it might look nice to a new user who doesn't like
> to see a lot of options they don't necessarily understand, but it
> wastes the time of more experienced users.
I think we should use "[X] OptionMenu -->" variant USB Gadgets use
where possible. Currently for example IDE code is
ATA/ATAPI/MFM/RLL support -->
<*> ATA/ATAPI/MFM/RLL support
IDE, ATA and ATAPI Block devices -->
<*> Enhandced IDE/MFM/RLL disk/cdrom/...
One level can be completely removed by doing
<*> ATA/ATAPI/MFF/RLL support -->
directly in toplevel menu. Then you do not have to open most of
the menus, as if there is no checkmark before submenu entry, there is
definitely nothing selected below.
And after all, there is also "make menuconfig MENUCONFIG_MODE=single_menu".
Unfortunately it starts with all nodes closed, and '*' (which I'm used
to use for unrolling complete subtree) does nothing. And
second problem is that "<*> XXX -->" does not work as expected in
single_menu mode, it still creates its own submenu, which kinda complicates
things.
Best regards,
Petr Vandrovec
next prev parent reply other threads:[~2003-07-24 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 19:10 some kernel config menu suggested tweaks John Bradford
2003-07-24 19:53 ` Petr Vandrovec [this message]
2003-07-26 12:52 ` Tomas Szepe
2003-07-26 13:07 ` Robert P. J. Day
2003-07-26 13:19 ` Loading of modules fails while using kernel 2.6.0-test1 Manjunathan Padua Yellappan
2003-07-26 13:29 ` Felipe Alfaro Solana
2003-07-26 13:34 ` Manjunathan Padua Yellappan
2003-07-26 14:33 ` some kernel config menu suggested tweaks Tomas Szepe
-- strict thread matches above, loose matches on Subject: below --
2003-07-26 15:20 John Bradford
2003-07-24 18:45 John Bradford
2003-07-24 18:49 ` Robert P. J. Day
2003-07-24 17:05 Robert P. J. Day
2003-07-26 12:14 ` Tomas Szepe
2003-07-26 12:30 ` Robert P. J. Day
2003-07-26 13:01 ` Tomas Szepe
2003-07-26 13:45 ` Randy.Dunlap
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=20030724195322.GA8194@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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;
as well as URLs for NNTP newsgroup(s).