{"thread":{"id":"7880","subject":"[PATCH] make j/k move down/up in gitk (like vi)","startedAt":"2007-04-28T03:02:15Z","lastAt":"2007-04-29T18:13:16Z","messageCount":3,"participants":["Bart Trojanowski","Martin Waitz","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"40645","messageId":"20070428030215.GZ26786@jukie.net","threadId":"7880","inReplyTo":null,"subject":"[PATCH] make j/k move down/up in gitk (like vi)","fromName":"Bart Trojanowski","fromEmail":"bart@jukie.net","sentAt":"2007-04-28T03:02:15Z","receivedAt":"2007-04-28T03:02:15Z","isPatch":true,"sender":{"key":"bart@jukie.net","avatar":"https://avatars.githubusercontent.com/u/6721?v=4"},"body":"Currently gitk has i/k bound to move up and down in the commit list.  I\nwould like to make that more consistent with vi's j/k.\n\nIf this is not acceptable, I will investigate a git-config option for vi\ncompatibility mode.\n\n---\n gitk |    6 ++----\n 1 files changed, 2 insertions(+), 4 deletions(-)\n\ndiff --git a/gitk b/gitk\nindex b1c65d7..0ce4a12 100755\n--- a/gitk\n+++ b/gitk\n@@ -711,10 +711,8 @@ proc makewindow {} {\n     bindkey n \"selnextline 1\"\n     bindkey z \"goback\"\n     bindkey x \"goforw\"\n-    bindkey i \"selnextline -1\"\n-    bindkey k \"selnextline 1\"\n-    bindkey j \"goback\"\n-    bindkey l \"goforw\"\n+    bindkey k \"selnextline -1\"\n+    bindkey j \"selnextline 1\"\n     bindkey b \"$ctext yview scroll -1 pages\"\n     bindkey d \"$ctext yview scroll 18 units\"\n     bindkey u \"$ctext yview scroll -18 units\"\n-- \n1.5.2.rc0.56.g6169a\n"},{"id":"40650","messageId":"20070428092608.GL9818@admingilde.org","threadId":"7880","inReplyTo":"20070428030215.GZ26786@jukie.net","subject":"Re: [PATCH] make j/k move down/up in gitk (like vi)","fromName":"Martin Waitz","fromEmail":"tali@admingilde.org","sentAt":"2007-04-28T09:26:08Z","receivedAt":"2007-04-28T09:26:08Z","isPatch":true,"sender":{"key":"tali@admingilde.org","avatar":"https://gravatar.com/avatar/3f89b03eee362187effabe257898735b475673a12265c398ea9161259ae91553?d=mp&s=160"},"body":"hoi :)\n\nOn Fri, Apr 27, 2007 at 11:02:15PM -0400, Bart Trojanowski wrote:\n> Currently gitk has i/k bound to move up and down in the commit list.  I\n> would like to make that more consistent with vi's j/k.\n\nvery nice.\nif you want to keep back/forward near up/down you can use h/l, just like\nleft/right in vi.\n\n-- \nMartin Waitz\n"},{"id":"40702","messageId":"7vejm3dp6r.fsf@assigned-by-dhcp.cox.net","threadId":"7880","inReplyTo":"20070428030215.GZ26786@jukie.net","subject":"Re: [PATCH] make j/k move down/up in gitk (like vi)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-29T18:13:16Z","receivedAt":"2007-04-29T18:13:16Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Bart Trojanowski <bart@jukie.net> writes:\n\n> Currently gitk has i/k bound to move up and down in the commit list.  I\n> would like to make that more consistent with vi's j/k.\n\nI kind of second this.  Any program that implements keyboard\nnavigation and binds directions differently from vi greatly\nirritates me.\n\nBut it may be just me, who never used wordstar.\n\n> If this is not acceptable, I will investigate a git-config option for vi\n> compatibility mode.\n\nI think a sensible way to go would be to allow gitk to read a\ncustom tcl script from $HOME/.gitk, and make sure when the file\nis written back, the custom bindings are stored there as well.\n"}]}