From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Coleman <tutufan@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-diff should not fire up $PAGER, period!
Date: Thu, 18 Dec 2008 04:22:31 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.00.0812180419090.14632@racer> (raw)
In-Reply-To: <3c6c07c20812171818k6b6e3555ja991e20d74d8291b@mail.gmail.com>
Hi,
On Wed, 17 Dec 2008, Mike Coleman wrote:
> I still find git-diff's unsolicited invocation of $PAGER a bit
> jarring, but I also find that I like it.
It might have its reason in that it follows the common flow, where
interactive use of _any_ diff program is _just useless_ unless piped to a
pager.
And no, redirecting to a file is not interactive.
Can we please stop with those bogus and pointless, not to mention
uninformed, discussions about design decisions that have been verified to
be useful, or at least not harmful in any way, for a _long_, _long_ time?
The git list is high volume already, but at least so far it was high
signal/noise ratio.
Let's keep it that way,
Dscho
next prev parent reply other threads:[~2008-12-18 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:18 git-diff should not fire up $PAGER, period! Mike Coleman
2008-12-18 2:26 ` Junio C Hamano
2008-12-18 3:22 ` Johannes Schindelin [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-16 0:56 git-diff should not fire up $PAGER if there is no diff Jeff King
2008-12-17 21:45 ` git-diff should not fire up $PAGER, period! jidanni
2008-12-17 22:02 ` Junio C Hamano
2008-12-17 22:04 ` Linus Torvalds
2008-12-22 3:28 ` Miles Bader
2008-12-18 3:31 ` Jeff King
2008-12-22 3:27 ` Miles Bader
2008-12-22 7:55 ` Johannes Sixt
2008-12-22 8:30 ` Junio C Hamano
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=alpine.DEB.1.00.0812180419090.14632@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tutufan@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox