git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Michon <emmanuel_michon@sigmadesigns.com>
To: <git@vger.kernel.org>
Subject: (minor concern) git using the pager should not be a default
Date: Wed, 29 Aug 2012 18:02:06 +0200	[thread overview]
Message-ID: <503E3CFE.1080603@sigmadesigns.com> (raw)

Hello,

I'm risking myself on this mailing list after looking for some advise on
IRC. Basically I know about this previous attempt
http://marc.info/?l=git&m=122955045415845&w=2 but my request has little
to do with emacs.

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].

As far as I understand those, stdin/out/err would be better left with
minimum processing. Silent execution with $? = 0 is the best thing that
can happen.

Per those rules, which I think apply to Linux apps, it would be
preferrable if the *default* setup of git didn't fork a pager, didn't
use colors, didn't behave differently whether piped or not.

Of course I would be the first to always call the tool with
git diff |less
excepted when I do git diff |diffstat
or enjoy such options as command line or environment switches to git.
when I want.

So the point is more about the appropriateness of pushing that special
ergonomy to all users, knowing it makes most users happy.

Isn't the design principle superior to the wishes of the masses?

Thanks for reading,
Don't laugh,
Keep on the good work.

Sincerely yours,

e.m.

             reply	other threads:[~2012-08-29 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 16:02 Emmanuel Michon [this message]
2012-08-29 17:19 ` (minor concern) git using the pager should not be a default Junio C Hamano
2012-08-29 17:50 ` Junio C Hamano
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=503E3CFE.1080603@sigmadesigns.com \
    --to=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).