From: Michal Marek <mmarek@suse.cz>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Rob Landley <rob@landley.net>,
Ramkumar Ramachandra <artagnon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] menuconfig: Allow j/k to move down/up the menu
Date: Wed, 10 Jul 2013 16:56:01 +0200 [thread overview]
Message-ID: <51DD7601.5090200@suse.cz> (raw)
In-Reply-To: <478d866c-606e-42de-9779-6ae18d70e7f1@CO1EHSMHS014.ehs.local>
Dne 9.7.2013 01:08, Sören Brinkmann napsal(a):
> On Sat, Jul 06, 2013 at 06:00:05PM -0500, Rob Landley wrote:
>> On 07/05/2013 06:32:59 AM, Ramkumar Ramachandra wrote:
>>> Like in Vim.
>>>
>>> Cc: Michal Marek <mmarek@suse.cz>
>>> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
>>> ---
>>> Unsure why nobody has done this yet.
>>
>> While you're at it, why don't you add the ws up and down bindings
>> from World of Warcraft?
>>
[...]
> 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.
One issue here is that j and k are already taken. Letters other than
h/m/n/y are used as hotkeys in menuconfig/nconf, if there is a menu item
starting with the respective letter. So at a minimum, the patch would
have to add j and k to the reserved set.
Michal
prev parent reply other threads:[~2013-07-10 14:56 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
2013-07-10 14:56 ` Michal Marek [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=51DD7601.5090200@suse.cz \
--to=mmarek@suse.cz \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=soren.brinkmann@xilinx.com \
/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.