| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <51DC4541.8010409@stranner.org> Date: Tue, 09 Jul 2013 19:15:45 +0200 From: Heimo Stranner <heimo@...anner.org> To: Steven Noonan <steven@...inklabs.net> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH] menuconfig: Allow j/k to move down/up the menu On 2013-07-09 19:07, Steven Noonan wrote: > On Tue, Jul 9, 2013 at 9:55 AM, Heimo Stranner <heimo@...anner.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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists