From: Dirk Gouders <dirk@gouders.net>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [RFC] mconf: mark empty menus/menuconfigs different form non-empty ones
Date: Sun, 19 May 2013 18:22:05 +0200 [thread overview]
Message-ID: <ghzjvrkkia.fsf@mx10.gouders.net> (raw)
In-Reply-To: <20130519090855.GA3359@free.fr> (Yann E. MORIN's message of "Sun, 19 May 2013 11:08:55 +0200")
"Yann E. MORIN" <yann.morin.1998@free.fr> writes:
> Dirk, All,
>
> On 2013-05-17 12:28 +0200, Dirk Gouders spake thusly:
>> here is a patch for the scheme you suggested.
>>
>> I also tried how it looks if empty submenus are maked by "---|" but I
>> think that is a matter of personal preferences and I don't want to try to
>> anticipate what users who use mconf heavily want.
>
> I suggested '----' to floow the scheme for booleans and tristates:
> [ ] Selectable boolean
> < > Selectable tristate
> { } Selectable tristate, forced to at least M
> - - Unselectable tristate, forced to Y
>
> So I think '----' is a nice fit for '--->'.
Thanks for the explatation, Yann. Now, I understand why you suggested
exactly that scheme.
Dirk
prev parent reply other threads:[~2013-05-19 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:05 [RFC] mconf: suppress empty submenus Dirk Gouders
2013-05-15 14:05 ` [PATCH] " Dirk Gouders
2013-05-16 8:24 ` [RFC] " Dirk Gouders
2013-05-16 23:04 ` Yann E. MORIN
2013-05-17 4:22 ` Dirk Gouders
2013-05-17 10:28 ` [RFC] mconf: mark empty menus/menuconfigs different form non-empty ones Dirk Gouders
2013-05-17 10:28 ` [PATCH] " Dirk Gouders
2013-05-17 12:42 ` [PATCH v2] mconf/nconf: mark empty menus/menuconfigs different from " Dirk Gouders
2013-05-19 15:14 ` Yann E. MORIN
2013-05-19 19:49 ` [PATCH v3] " Dirk Gouders
2013-05-20 15:50 ` Yann E. MORIN
2013-05-19 9:08 ` [RFC] mconf: mark empty menus/menuconfigs different form " Yann E. MORIN
2013-05-19 16:22 ` Dirk Gouders [this message]
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=ghzjvrkkia.fsf@mx10.gouders.net \
--to=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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