From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: menuconfig search (Re: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp)
Date: Mon, 3 Apr 2006 22:15:37 -0700 [thread overview]
Message-ID: <20060403221537.79bb3af9.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0603301022400.30783@yvahk01.tjqt.qr>
On Thu, 30 Mar 2006 10:24:30 +0200 (MEST) Jan Engelhardt wrote:
> >Most people don't seem to know
> >about '/' in make menuconfig.
That's a shame.
> I find it very confusing to use, since it returns too verbose text to skim
> through. Probably the search function should be split into "only search
> titles[*]" and "search description too".
Re verbosity: do you know that menuconfig search (/) takes regular
expressions? That could help someone limit the amount of output
from it.
Can you give an example of being too verbose?
> config UNIX
> bool "Unix socket" <-- that's a "title", as in menuconfig
The search function of menuconfig (currently) works in the namespace of
CONFIG_ symbols. It will search for a regex in the symbol tables.
Yes, someone could modify it to search thru the prompt strings of the
symbols. I don't know if that would help or not.
I have just modified menuconfig search to make displaying the
Selects: and Selected by: output be an option (actually it's a
different search command (\) to not see those lines.
Would that help any regarding verbosity?
The patch is here if you would care to try it:
http://www.xenotime.net/linux/patches/menuconfig-search2.patch
---
~Randy
next prev parent reply other threads:[~2006-04-04 5:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 22:08 [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Pavel Machek
2006-03-29 22:47 ` Andrew Morton
2006-03-29 23:09 ` Ashok Raj
2006-03-29 23:36 ` Nigel Cunningham
2006-03-29 23:47 ` Ashok Raj
2006-03-29 23:53 ` Nigel Cunningham
2006-03-30 0:12 ` Ashok Raj
2006-03-30 0:32 ` Nigel Cunningham
2006-03-30 0:13 ` Andrew Morton
2006-03-30 0:18 ` Nigel Cunningham
2006-03-30 3:01 ` Nigel Cunningham
[not found] ` <20060330030657.GA10405@mars.ravnborg.org>
2006-03-30 10:11 ` Roman Zippel
2006-03-30 8:24 ` Jan Engelhardt
2006-04-04 5:15 ` Randy.Dunlap [this message]
2006-04-04 6:01 ` menuconfig search (Re: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp) Alexey Dobriyan
2006-04-04 15:12 ` Randy.Dunlap
2006-04-08 8:42 ` Jan Engelhardt
2006-04-09 2:29 ` Randy.Dunlap
2006-04-11 11:18 ` Jan Engelhardt
2006-03-30 8:41 ` [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Pavel Machek
2006-03-30 16:17 ` Rafael J. Wysocki
2006-03-29 0:30 ` Pavel Machek
2006-04-01 23:55 ` Ashok Raj
2006-03-30 3:24 ` Andrew Morton
2006-03-30 13:00 ` Ashok Raj
2006-03-30 13:17 ` Pavel Machek
2006-03-30 13:05 ` Eric W. Biederman
2006-03-30 8:30 ` Pavel Machek
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=20060403221537.79bb3af9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®