On Jul 19, 2007, at 7:02 AM, martin f krafft wrote:
+1 on the patch, but I also wonder why use of a pager is default in git anyway. At least I find it to be contrary to what I am used to on the Unix command line. For reference, there was an argument about this in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424978, which includes a long IRC log in German, unfortunately, where a bunch of people agreed with my proposal *not* to use a pager by default, since it makes it difficult to use information from the output to assemble the next command on the command line. Every terminal in use nowadays can easily scroll and even search back 250 lines with the added benefit of not randomly clearing the screen when you quit $PAGER.
I think it's because much of the core git community lives more on the console or simple terminals like xterm than in something with easy search and scrolling features like konsole or Terminal.app. Git output tends to become very long very quickly, and usually you want to start reading from the beginning.
Many command line tools either output small chunks of input (ls, in most directories), output slowly (make), or their input is mostly only important when it errors out (make). Git's output tends to be quite long and have the most relevant (read: recent) information at the beginning so paging is pretty much a must, instead of an occasional need.
If someone thinks that git paging by default is obnoxious, it just takes running "git config --global core.pager cat". Now, no more paging. If you find your $PAGER clearing the screen when quitting obnoxious, I suggest checking your configuration. In particular, I find setting $LESS to "FX" (at least) to be most useful.
~~ Brian - 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
