From: Heimo Stranner <heimo@stranner.org>
To: Steven Noonan <steven@uplinklabs.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] menuconfig: Allow j/k to move down/up the menu
Date: Tue, 09 Jul 2013 19:15:45 +0200 [thread overview]
Message-ID: <51DC4541.8010409@stranner.org> (raw)
In-Reply-To: <CAKbGBLgrTtMfkg9VEiQ=5JPzJvCUa5bPUjPHVswZFxviY1BKdg@mail.gmail.com>
On 2013-07-09 19:07, Steven Noonan wrote:
> On Tue, Jul 9, 2013 at 9:55 AM, Heimo Stranner <heimo@stranner.org> wrote:
>>> Well, one advantage of these key bindings is, that you don't have to
>>> move your hands away from the base line. And as vim user I find myself
>>> using vim key sequences in all tools. I cannot even count how many
>>> processes I accidentally killed because I tried to scroll using 'k' in
>>> htop where it does 'kill'.
>>>
>>> In a nutshell: I'm all for vim key bindings everywhere!
>>>
>> I can't agree more!
>>
>> Because vim key bindings are rather common I can't see a problem if this
>> patch is applied.
> The biggest problem I see is the conflict between j/k and the letter
> shortcuts used to jump to specific menu items (the letter highlighted
> in blue on each item). But I haven't ever used that functionality in
> practice, so who knows.
I haven't thought about that. Obviously you are right, "Kernel hacking"
and "Kernel compression mode" just being two examples that use k which I
found in a very quick search.
next prev parent reply other threads:[~2013-07-09 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 11:32 [PATCH] menuconfig: Allow j/k to move down/up the menu Ramkumar Ramachandra
2013-07-06 23:00 ` Rob Landley
2013-07-07 18:30 ` Ramkumar Ramachandra
2013-07-08 23:08 ` Sören Brinkmann
2013-07-09 16:27 ` Rob Landley
2013-07-09 16:55 ` Heimo Stranner
2013-07-09 17:07 ` Steven Noonan
2013-07-09 17:15 ` Heimo Stranner [this message]
2013-07-10 14:56 ` Michal Marek
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=51DC4541.8010409@stranner.org \
--to=heimo@stranner.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steven@uplinklabs.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.