threads / discuss / 16747

Re: git-diff should not fire up $PAGER if there is no diff

Subject: Re: git-diff should not fire up $PAGER if there is no diff

## tl;dr

3 messages between Dec 16, 2008 and Dec 16, 2008.

replies: 2people: 2as markdown or json

jidanni@jidanni.org· Dec 16, 2008, 01:16 UTC · lore
>>>>> "JS" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

JS> Maybe you are not aware just how annoying these "this should do that, that JS> should do this" without a patch are?

Yes but I must first learn the thing I am about to make a patch for.
In the mean time I could like most beginners, just feel dumb.

Or I could let you have my valuable insights on how things look to a beginner. You would else have no way of knowing. Sorry I always come across as Don Rickles the pushy customer... it's all a charade... now let's get back to business,

>>>>> "JK" == Jeff King <peff@peff.net> writes:

JK> The usual workaround is to ask the pager to exit immediately if the JK> output is small. I.e., putting "F" in your LESS variable (which git does JK> automatically if you don't already have LESS set).

Ah, but who doesn't have LESS set these days? OK, the man page should mention that so people will put the F on their LESS variable, like I recall another man page already does.

Jeff King· Dec 16, 2008, 04:07 UTC · re: jidanni@jidanni.org · lore
On Tue, Dec 16, 2008 at 09:16:29AM +0800, jidanni@jidanni.org wrote:
Show 7 quoted lines
> JK> The usual workaround is to ask the pager to exit immediately if the
> JK> output is small. I.e., putting "F" in your LESS variable (which git does
> JK> automatically if you don't already have LESS set).
> 
> Ah, but who doesn't have LESS set these days? OK, the man page should
> mention that so people will put the F on their LESS variable, like I
> recall another man page already does.
Not unreasonable. Care to make a patch to the documentation?
-Peff

← back to recent threads