Jonas Fonseca <fonseca@xxxxxxx> writes: > On Mon, Feb 9, 2009 at 23:30, Peter Baumann <waste.manager@xxxxxx> wrote: > >> On Mon, Feb 09, 2009 at 05:22:36PM -0500, Jeff King wrote: >>> Don't the up and down arrows switch the commit (updating the diff pane >>> as appropriate), and PgUp/PgDown scroll the diff window (I don't know >>> the actual function names, but you should be able to even rebind these >>> in your tigrc if you want). >> >> Damn. I'm so used to the vi keybindings pressing j/k to move down/up >> that I didn't check the cursor keys. > > Well, initially tig worked similar to what you expected and a program > like slrn, where up/down (or j/k) moves between articles (commits) and > you have to press enter to actually show/load the commit in the diff > view. This mode might be more natural, and Jari has argued that it > would make tig (and it's many forks) more bearable to on Cygwin > running on an old PC. It also helps when you want to see only particular commit; you scroll to correct location as ask display by pressing RET. If aut-update is in effect, the other commits in between tie up the cursor movement, especially if the history is long: tap, tap, tap .... and you'd have to wait for all all screen to update line by line. Idea: The auto-update feature could be even turned on/off with a command-key . But an comand line option would do for me, as long as the behaviot is configurable. It is slow under Cygwin, especially on networked case, where Cygwin resides on remote disk, not the local one. Jari -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
