Hi, On Tue, May 30, 2017 at 01:16:11PM +0100, John Lane wrote: > I just wondered why you allocated "K" to move LEFT along the tabs and > "J" to move RIGHT ?
Because J is the vim-keybinding to go down, and it makes a lot of sense to map "down" to "next"/"right". Also, with vertical tabs (:set tabs position left) it'd be confusing if J/down would go up. > I realise it's personal preference, but was just curious why you chose > to do it the way you did...? Not entirely. It's what dwb does, and qutebrowser's keybindings are designed to be compatible with dwb's, because it originally was a replacement for many stranded dwb users (such as myself). > Also, any reason why you never implemented ':x' as well as ':wq' which > is, I believe, standard vi ? :wq is aliased, :x isn't. Generally because qutebrowser is not vi, and with some things it just doesn't make sense to try to shoehorn them into qutebrowser. Even :wq is questionable - what do you expect "write" to do in a browser? Florian -- https://www.qutebrowser.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
