On 30/05/17 13:20, Florian Bruhin wrote: > > 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 think that is a good point. I hadn't tried moving the tabs to the left. Have just done so although I am worried it will lead to bad habits - just how many tabs will fit down there!!! :)
> > 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). > that too is a fair enough, and probably the primary reason! >> 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? > My assumption was that :wq exited saving session/settings whereas :q didn't (haven't checked this though). And I have years' muscle-memory calling for :x over :wq. I have aliased this myself in qutebrowser.conf. Cheers for the response. John
