From: Randy Dunlap <randy.dunlap@oracle.com>
To: nir.tzachar@gmail.com
Cc: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, sam@ravnborg.org,
randy.dunlap@oracle.com
Subject: Re: [PATCH] nconfig: add search support
Date: Thu, 5 Aug 2010 10:04:08 -0700 [thread overview]
Message-ID: <20100805100408.5b724047.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1280838492-9942-1-git-send-email-nir.tzachar@gmail.com>
On Tue, 3 Aug 2010 15:28:12 +0300 nir.tzachar@gmail.com wrote:
> From: Nir Tzachar <nir.tzachar@gmail.com>
>
> Remove the old hotkeys feature, and replace by a regular string search.
> Behaviour of search is as advised by Sam.
>
> From nconfig help:
>
> Searching: pressing '/' triggers search mode. nconfig performs a
> regular string compare, case insensitive, starting at
I would say: simple string compare
"regular" has no meaning (at least for me) there.
> the beginning of each menu line.\n"
> Pressing the up/down keys highlights the previous/next
> matching item. Backspace removes one character from the
> match string. Pressing either '/' again or ESC exits\
> search mode. All other keys behave normally.
>
> Miscellaneous other changes (including Rundy's Justin's input).
Yes, the bottom menu and the typos are fixed. Thanks.
However, I'm not finding this terribly useful, mostly due to it starting
comparison at the beginning of each menu line.
E.g., I'd like to be able to find "emulations" in the top-level menu here:
Executable file formats / Emulations --->
or I'd like to be able to find "crc" menu items in any sub-menu.
Maybe I should just stick to config symbol searches. I don't think it's all
that likely that people will know how each menu line text begins.
As for the search UI, I'd rather that it be presented like the symbol search,
in a box, instead of just a single line at the top of the screen.
> Signed-off-by: Nir Tzachar <nir.tzachar@gmail.com>
> ---
> scripts/kconfig/nconf.c | 350 +++++++++++++++++++++++++------------------
> scripts/kconfig/nconf.gui.c | 20 ++--
> scripts/kconfig/nconf.h | 3 +-
> 3 files changed, 213 insertions(+), 160 deletions(-)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-05 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik1p0oK=-msd0a-4wA88Z-Cv29qHVNUYeEETcJD@mail.gmail.com>
2010-08-01 7:20 ` [PATCH] nconfig: add search support nir.tzachar
2010-08-01 9:28 ` Sam Ravnborg
2010-08-01 10:21 ` Nir Tzachar
2010-08-01 11:49 ` Sam Ravnborg
2010-08-02 16:32 ` Randy Dunlap
2010-08-03 4:37 ` Nir Tzachar
2010-08-02 21:22 ` rdunlap
2010-08-03 4:41 ` Nir Tzachar
2010-08-03 12:28 ` nir.tzachar
2010-08-05 17:04 ` Randy Dunlap [this message]
2010-08-05 18:13 ` Nir Tzachar
2010-08-05 18:19 ` Randy Dunlap
2010-08-06 12:41 ` Nir Tzachar
2010-08-06 13:54 ` Sam Ravnborg
2010-08-06 19:22 ` Nir Tzachar
2010-08-06 14:09 ` Sam Ravnborg
2010-08-08 13:50 nir.tzachar
2010-08-08 15:37 ` Sam Ravnborg
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=20100805100408.5b724047.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nir.tzachar@gmail.com \
--cc=sam@ravnborg.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