git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emmanuel Michon <emmanuel_michon@sigmadesigns.com>
Cc: <git@vger.kernel.org>
Subject: Re: (minor concern) git using the pager should not be a default
Date: Wed, 29 Aug 2012 10:50:19 -0700	[thread overview]
Message-ID: <7vd329wpt0.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <503E3CFE.1080603@sigmadesigns.com> (Emmanuel Michon's message of "Wed, 29 Aug 2012 18:02:06 +0200")

Emmanuel Michon <emmanuel_michon@sigmadesigns.com> writes:

> I believe UNIX recommends some rules in the «less is more» spirit when
> designing command line applications [basically listed here:
> http://en.wikipedia.org/wiki/Unix_philosophy].

That is exactly why our plumbing layer of commands (e.g. "git
diff-tree", "git rev-list") do not page by default for people who
want to go bare-metal Unix philosophy.

In other words, Porcelain (roughly speaking, those that page by
default when their standard output is terminal), are not "command
line applications"; they have a layer on top with a built-in UI.

If you follow Unix philosophy and want to combine tools each of
which is designed to do one thing and one thing well, you would be
using the commands from the plumbing layer to write your scripts,
and wouldn't have to raise that "minor concern" in the first place,
as they do not page by default ;-).

  parent reply	other threads:[~2012-08-29 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 16:02 (minor concern) git using the pager should not be a default Emmanuel Michon
2012-08-29 17:19 ` Junio C Hamano
2012-08-29 17:50 ` Junio C Hamano [this message]
2012-08-31 17:54   ` dag
2012-08-31 18:09     ` Andreas Schwab
2012-08-31 21:43       ` Jeff King
2012-08-31 23:03         ` dag
2012-08-31 18:48     ` 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=7vd329wpt0.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=emmanuel_michon@sigmadesigns.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).