From: Yuval Turgeman <yuvalt@gmail.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Searching parameters in menuconfig
Date: Tue, 31 Aug 2004 18:12:20 +0300 [thread overview]
Message-ID: <9ae345c00408310812212e371e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408311427110.981@scrub.home>
On Tue, 31 Aug 2004 16:33:36 +0200 (CEST), Roman Zippel
<zippel@linux-m68k.org> wrote:
> Andrew already commented on the coding style, so I can skip that.
Yeah sorry about that... I didn't read the CodingStyle doc... I'll pay
more attention to it from now on.
> You get to this information easier by iterating over the properties
> attached to a symbol (sym->prop) and a symbol can have multiple menu
> prompts, you show only the first one (which might not be the right one)
> and sym->prop->text might not even be a menu prompt at all.
Ok, I wasn't aware that a symbol could be located in several submenus
- I just tried to follow the build_conf routine.
> It would be nice to actually make it really useful, by first building a
> list of found symbols (and possibly allow wildcards for searching) and
> generate a menu of this. After a symbol is selected, build a new menu with
> all the prompts, which could also include the option to change parent
> symbols.
Yeah I tought about it also - I guess I'll try to implement this soon.
The usability of the search can be improved a lot... this was just a
tiny prototype to help me find the parameter i was missing. :-)
Thanks!
--
Yuval Turgeman
prev parent reply other threads:[~2004-08-31 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 7:52 [PATCH] Searching parameters in menuconfig Yuval Turgeman
2004-08-31 9:08 ` Andrew Morton
2004-08-31 14:33 ` Roman Zippel
2004-08-31 15:12 ` Yuval Turgeman [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=9ae345c00408310812212e371e@mail.gmail.com \
--to=yuvalt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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