From: jidanni@jidanni.org
To: git@vger.kernel.org
Subject: Re: git-diff should not fire up $PAGER if there is no diff
Date: Tue, 16 Dec 2008 09:16:29 +0800 [thread overview]
Message-ID: <87oczcx6ky.fsf@jidanni.org> (raw)
In-Reply-To: alpine.DEB.1.00.0812160153340.14632@racer
>>>>> "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.
next parent reply other threads:[~2008-12-16 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.00.0812160153340.14632@racer>
2008-12-16 1:16 ` jidanni [this message]
2008-12-16 4:07 ` git-diff should not fire up $PAGER if there is no diff Jeff King
2008-12-16 17:38 ` jidanni
2008-12-16 0:21 jidanni
2008-12-16 0:56 ` Jeff King
2008-12-16 6:35 ` Stefan Karpinski
2008-12-16 7:44 ` Jeff King
2008-12-16 22:43 ` Stefan Karpinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oczcx6ky.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.