summaryrefslogtreecommitdiff
path: root/gitk-git/gitk
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2011-09-19 16:49:50 (GMT)
committerPaul Mackerras <paulus@samba.org>2011-10-08 07:01:54 (GMT)
commit811c70fc8369cfeae2f1e843c695c37e3b0c3109 (patch)
tree66d01cc1090de14d6095cf08e7d8b27717b2efb5 /gitk-git/gitk
parentde665fd3cfee674a62818246dfb158ecf81b2b76 (diff)
downloadgit-811c70fc8369cfeae2f1e843c695c37e3b0c3109.zip
git-811c70fc8369cfeae2f1e843c695c37e3b0c3109.tar.gz
git-811c70fc8369cfeae2f1e843c695c37e3b0c3109.tar.bz2
gitk: Make vi-style keybindings more vi-like
When commit 6e2dda35 (Add new keybindings, 2005-09-22) added vi-style keybindings to gitk (an excellent idea!), instead of adopting the usual "hjkl = left, down, up, right" bindings used by less, vi, rogue, and many other programs, it used "ijkl = up, left, down, right" to mimic the inverted-T formation of the arrow keys on a qwerty keyboard, in the style of Lode runner. So using 'j' and 'k' to scroll through commits produces utterly confusing results to the vi user, as 'k' moves down and 'j' moves to the previous commit. Luckily most non-vi-users are probably using an alternate set of keys (cursor keys or z/x + n/p) anyway. Switch to the expected vi/nethack convention. Requested-by: Josh Triplett <josh@joshtriplett.org> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'gitk-git/gitk')
0 files changed, 0 insertions, 0 deletions