From: Dirk Gouders <dirk@gouders.net>
To: linux-kbuild@vger.kernel.org
Subject: Re: [RFC] mconf: suppress empty submenus
Date: Thu, 16 May 2013 10:24:58 +0200 [thread overview]
Message-ID: <gihai3uyat.fsf@karga.hank.lab> (raw)
In-Reply-To: <1368626738-31911-1-git-send-email-dirk@gouders.net> (Dirk Gouders's message of "Wed, 15 May 2013 16:05:37 +0200")
Dirk Gouders <dirk@gouders.net> writes:
> Hello,
>
> I noticed that sometimes it happens that there are empty
> submenus, and I tried to see if they can't be suppressed
> by mconf (if not explicitely done by the kbuild-language).
>
> Well, I am not sure if someone wants this change and also
> if I realized all possible situations and therefore the
> patch is not meant to be accepted as is but as a proof-of-concept.
>
> Because of that I implemented the changes as a new function
> menu_is_visible_new() and a helper function that walks the whole menu
> structure and compares the results of the old and the new function.
>
> I also tried to add coments to the new function which reflect
> my understanding but of course might be incomplete or even wrong.
>
> I'd be glad if someone takes the time to test and/or review
> the code or comment on the sanity of such a change.
>
> Attached is an example output of the helper function (i.e.
> empty dialogs that would be suppressed by the menu_is_visible_new()).
Sorry, I noticed the first problem with one potential user (nconfig) of
such a change: with `nconfig' one cannot enter those hidden empty
submenus even when turning on all options with (F4), in which case the
submenu wouldn't be empty.
So, for a complete proof-of-concept I need to do some more work which I
think should also contain a proof that the setting of the
SYMBOL_DEF_USER flag behaves exactly the same as before.
Dirk
PS: In the original message, `sed s/kbuild/kconfig/', of course.
next prev parent reply other threads:[~2013-05-16 8:25 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 ` Dirk Gouders [this message]
2013-05-16 23:04 ` [RFC] " 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
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=gihai3uyat.fsf@karga.hank.lab \
--to=dirk@gouders.net \
--cc=linux-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.