From: Rob Landley <rob@landley.net>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] menuconfig: Allow j/k to move down/up the menu
Date: Tue, 09 Jul 2013 11:27:53 -0500 [thread overview]
Message-ID: <1373387273.27613.30@driftwood> (raw)
In-Reply-To: <478d866c-606e-42de-9779-6ae18d70e7f1@CO1EHSMHS014.ehs.local> (from soren.brinkmann@xilinx.com on Mon Jul 8 18:08:41 2013)
On 07/08/2013 06:08:41 PM, Sören Brinkmann wrote:
> 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?
> >
> > The reason nobody has done this yet is that vi predates the
> > invention of cursor keys. They keyboards Bill Joy was using in the
...
> > And now you know _why_ Linux is over 20 years old and has never
> > needed this.
>
> 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'.
A ringing endorsement.
Rob
next prev parent reply other threads:[~2013-07-09 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 11:32 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 [this message]
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
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=1373387273.27613.30@driftwood \
--to=rob@landley.net \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome