also sprach Steven Grimm <koreth@xxxxxxxxxxxxx> [2007.07.19.1243 +0200]: > 'GIT_PAGER':: > - This environment variable overrides `$PAGER`. > + This environment variable overrides `$PAGER`. If it is set > + to an empty string or to the value "cat", git will not launch > + a pager. +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 am sure there is a reason for the choice of using a pager by default. Could we please either rethink this reason and possibly make it non-default, or alternatively add the reason to the FAQ? -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck spamtraps: madduck.bogus@xxxxxxxxxxx no micro$oft components were used in the creation or posting of this email. therefore, it is 100% virus free and does not use html by default (yuck!).
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)
