From: "Du, Changbin" <changbin.du@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: mmarek@suse.com, corbet@lwn.net, yann.morin.1998@free.fr,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig/mconf: add jumping tip in title of search result textbox
Date: Tue, 7 Feb 2017 11:10:33 +0800 [thread overview]
Message-ID: <20170207031033.GB32621@intel.com> (raw)
In-Reply-To: <87a89zbkb0.fsf@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
On Mon, Feb 06, 2017 at 02:00:51PM +0200, Jani Nikula wrote:
> On Mon, 06 Feb 2017, changbin.du@intel.com wrote:
> > From: Changbin Du <changbin.du@intel.com>
> >
> > Prompt user how to quickly jump to the item he/she is interested in.
>
> :o
>
> All these years. I... I didn't know. Thanks!
>
aha, me too! You know, back to the top menu then look into step by
step...
> > Signed-off-by: Changbin Du <changbin.du@intel.com>
> > ---
> > scripts/kconfig/mconf.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/scripts/kconfig/mconf.c b/scripts/kconfig/mconf.c
> > index 315ce2c..23d5681 100644
> > --- a/scripts/kconfig/mconf.c
> > +++ b/scripts/kconfig/mconf.c
> > @@ -443,10 +443,10 @@ static void search_conf(void)
> >
> > res = get_relations_str(sym_arr, &head);
> > set_subtitle();
> > - dres = show_textbox_ext(_("Search Results"), (char *)
> > - str_get(&res), 0, 0, keys, &vscroll,
> > - &hscroll, &update_text, (void *)
> > - &data);
> > + dres = show_textbox_ext(
> > + _("Search Results (type the number to jump)"),
> > + (char *)str_get(&res), 0, 0, keys, &vscroll,
> > + &hscroll, &update_text, (void *)&data);
>
> It would be even better and discoverable if this could be turned into a
> dialog menu, so that you could navigate the search results using arrow
> keys and hit enter to choose. But this is already an improvement.
>
Yes, that will have a better experience. :)
> > again = false;
> > for (i = 0; i < JUMP_NB && keys[i]; i++)
> > if (dres == keys[i]) {
>
> --
> Jani Nikula, Intel Open Source Technology Center
--
Thanks,
Changbin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-02-07 3:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 7:46 [PATCH 0/2] kconfig/mconf: propagate jumping function in search result view changbin.du
2017-02-06 7:46 ` [PATCH 1/2] kconfig/mconf: add jumping tip in title of search result textbox changbin.du
2017-02-06 12:00 ` Jani Nikula
2017-02-07 3:10 ` Du, Changbin [this message]
2017-02-06 7:46 ` [PATCH 2/2] Documentation/kconfig: add search jump feature description changbin.du
2017-02-06 14:42 ` Jim Davis
2017-02-07 3:06 ` Du, Changbin
2017-02-08 3:09 ` [PATCH v2 0/2] kconfig/mconf: propagate jumping function in search result view changbin.du
2017-03-06 10:28 ` Du, Changbin
2017-03-23 5:35 ` Du, Changbin
2017-03-23 10:17 ` Jani Nikula
2017-02-08 3:09 ` [PATCH v2 1/2] kconfig/mconf: add jumping tip in title of search result textbox changbin.du
2017-02-08 8:07 ` Jani Nikula
2017-02-08 3:09 ` [PATCH v2 2/2] Documentation/kconfig: add search jump feature description changbin.du
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=20170207031033.GB32621@intel.com \
--to=changbin.du@intel.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yann.morin.1998@free.fr \
/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