From: Dmitry Voytik <dvv.kernel@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: mmarek@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nconf: add j, k and l keys for menu navigation
Date: Sat, 22 Dec 2012 09:27:30 +0400 [thread overview]
Message-ID: <20121222052730.GA12608@voyt-hp> (raw)
In-Reply-To: <50D4C54D.8020700@codeaurora.org>
On Fri, Dec 21, 2012 at 12:23:41PM -0800, Stephen Boyd wrote:
> On 12/21/12 11:12, Dmitry Voytik wrote:
> > Add vi-style keys for menu navigation: press j/k for down/up navigation
> > and l for entering to a submenu. Unfortantely h key is reserved for
> > the items help.
>
> Maybe you can just add j/k for up/down and then use enter and backspace
> for right/left?
IMHO alternative l key for entering to a submenu will not harm.
next prev parent reply other threads:[~2012-12-22 5:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 19:12 [PATCH] nconf: add j, k and l keys for menu navigation Dmitry Voytik
2012-12-21 20:23 ` Stephen Boyd
2012-12-22 5:27 ` Dmitry Voytik [this message]
2012-12-28 18:51 ` Dmitry Voytik
2012-12-28 19:40 ` [PATCH] nconf: add vi-style command keys for the " Dmitry Voytik
2012-12-29 22:33 ` [PATCH 2/2] nconf: function keys line, change background color for better readability Roland Eggner
2013-01-14 22:20 ` Yann E. MORIN
2013-01-14 22:26 ` Yann E. MORIN
2012-12-29 22:34 ` [PATCH 1/2] nconf: add keybindings for vi-style menu navigation, rewrite help texts Roland Eggner
2013-01-08 22:04 ` Yann E. MORIN
2013-01-14 18:24 ` Yann E. MORIN
2013-01-15 16:10 ` Roland Eggner
2013-01-15 16:26 ` [PATCH v2 " Roland Eggner
2013-01-15 16:36 ` [PATCH v2stable " Roland Eggner
2013-01-15 17:39 ` Yann E. MORIN
2013-01-15 22:27 ` [PATCH v2 " Yann E. MORIN
2013-01-16 20:19 ` Roland Eggner
2013-01-16 12:48 ` Michal Marek
2013-01-08 21:57 ` [PATCH] nconf: add vi-style command keys for the menu navigation Yann E. MORIN
2013-01-14 22:10 ` Yann E. MORIN
2013-01-15 17:12 ` Roland Eggner
2013-01-15 17:38 ` Yann E. MORIN
2013-01-15 17:55 ` Roland Eggner
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=20121222052730.GA12608@voyt-hp \
--to=dvv.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sboyd@codeaurora.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