public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] menuconfig: Search from everywhere
Date: Wed, 11 Feb 2015 18:29:06 +0100	[thread overview]
Message-ID: <1423675746.21685.53.camel@x220> (raw)
In-Reply-To: <1423487532-27968-1-git-send-email-kuleshovmail@gmail.com>

[Removed Yann. Web searches should explain why.]

On Mon, 2015-02-09 at 19:12 +0600, Alexander Kuleshov wrote:
> If we want to see search window again, for example after typo
> or for another search, we need to press on '< Exit >' and than
                                                            then

> execute new search. Let's make '/' active everywhere.

Everywhere or just in the "Search Results" screen itself?

A drawback of menuconfig is its stacked interface. Each search and jump
pushes two screens to its stack of screens. I'm often surprised at the
number of screens I generated by searching around a bit. Does searching
from withing search results again push another screen onto the stack?

Anyhow, if hitting enter and "/" bothers you a redesign of the search
functionality would be a better idea. Eg, make it have a input area on
top (to type in the query) and an text area below it (to display
results). Which is probably not worth the, presumably rather big,
effort.

> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
>  scripts/kconfig/lxdialog/textbox.c | 4 ++++
>  scripts/kconfig/mconf.c            | 8 ++++++++
>  2 files changed, 12 insertions(+)
> 
> diff --git a/scripts/kconfig/lxdialog/textbox.c b/scripts/kconfig/lxdialog/textbox.c
> index 1773319..958770d 100644
> --- a/scripts/kconfig/lxdialog/textbox.c
> +++ b/scripts/kconfig/lxdialog/textbox.c
> @@ -141,6 +141,10 @@ do_resize:
>  	while (!done) {
>  		key = wgetch(dialog);
>  		switch (key) {
> +		case '/':
> +			key = 9;
> +			done = true;
> +			break;
>  		case 'E':	/* Exit */
>  		case 'e':
>  		case 'X':
> diff --git a/scripts/kconfig/mconf.c b/scripts/kconfig/mconf.c
> index 4dd3755..d49fa45 100644
> --- a/scripts/kconfig/mconf.c
> +++ b/scripts/kconfig/mconf.c
> @@ -446,7 +446,15 @@ again:
>  					str_get(&res), 0, 0, keys, &vscroll,
>  					&hscroll, &update_text, (void *)
>  					&data);
> +		if (dres == 9) {
> +			free(sym_arr);
> +			str_free(&title);
> +			list_del(trail.prev);
> +			str_free(&sttext);
> +			search_conf();
> +			return;
> +		}
> +
>  		again = false;
>  		for (i = 0; i < JUMP_NB && keys[i]; i++)
>  			if (dres == keys[i]) {

Thanks,


Paul Bolle


      reply	other threads:[~2015-02-11 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 13:12 [PATCH] menuconfig: Search from everywhere Alexander Kuleshov
2015-02-11 17:29 ` Paul Bolle [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=1423675746.21685.53.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --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