git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dario Rodriguez <soft.d4rio@gmail.com>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] Fix for default pager
Date: Mon, 7 Jun 2010 23:14:58 -0300	[thread overview]
Message-ID: <AANLkTinydWk3GqGDww8FS7pmW16jAVazRkmT_GsRMIhy@mail.gmail.com> (raw)
In-Reply-To: <1275955270-sup-2380@pinkfloyd.chass.utoronto.ca>

On Mon, Jun 7, 2010 at 9:04 PM, Ben Walton <bwalton@artsci.utoronto.ca> wrote:
>
> Why not set a sensible DEFAULT_PAGER value for the system in your
> config.mak file instead?
>
> Just curious.
>

I was thinking about it before coding the patch, and found some
consequences. First of all, the most important thing I should
understand is that most users will install git from binary,
precompiled packages instead of the good download and compile. So this
is actually a good reason to not do it that way (config.mak)... Some
users may download the compiled binary while it's actually calling
it's default pager.

But this is not the only reason. Let me give you an example: We
develop (I'm actually working at Accenture) using several machines.
When we need some tool, we compile it in our first machine, and
install it for an specific user. In some other environments we cannot
compile things (testing environments) so we transfer (FTP) those
binary files. It's just another case, and the default pager could
cause problems here (in fact, i experienced such problems).

Another case (or something as the first one): If you installed less
(via your package system), then git, and then you happen to uninstall
less... should GIT be uninstalled in absence of it's default pager?

I think GIT must auto-detect it's pager based in what is on the system
at runtime, don't you think so?

  reply	other threads:[~2010-06-08  2:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Installing on AIX fails>
2010-06-07 23:58 ` [PATCH/RFC] Fix for default pager Dario Rodriguez
2010-06-08  0:04   ` Ben Walton
2010-06-08  2:14     ` Dario Rodriguez [this message]
2010-06-08  5:35       ` Jeff King
2010-06-08 13:49         ` Dario Rodriguez
2010-06-08 14:17           ` Johannes Sixt
2010-06-08 14:39             ` Dario Rodriguez
2010-06-08 15:56               ` Johannes Sixt
2010-06-08 17:28                 ` Dario Rodriguez
2010-06-08 18:59                   ` Johannes Sixt
2010-06-08 20:44                     ` Dario Rodriguez
2010-06-08 21:33                       ` Andreas Ericsson
2010-06-09  9:08                         ` Tor Arntsen
2010-06-09  9:29                           ` Miles Bader
2010-06-10  8:29                           ` Jeff King
2010-06-10  8:48                             ` Tor Arntsen
2010-06-10  8:59                               ` Jeff King
2010-06-10  9:24                                 ` Tor Arntsen
2010-06-10 11:31                                   ` Dario Rodriguez
2010-06-10 14:55                                 ` Junio C Hamano
2010-06-15 16:11                                 ` Brandon Casey
2010-06-15 16:32                                   ` Tor Arntsen
2010-06-16  1:34                                   ` Nazri Ramliy
2010-06-16  6:28                                   ` Jeff King
2010-06-09 18:57                         ` Ævar Arnfjörð Bjarmason
2010-06-08  5:29   ` Jeff King
2010-06-08  6:12     ` Johannes Sixt
2010-06-08 12:24     ` Dario Rodriguez
2010-06-08 14:04       ` Erik Faye-Lund

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=AANLkTinydWk3GqGDww8FS7pmW16jAVazRkmT_GsRMIhy@mail.gmail.com \
    --to=soft.d4rio@gmail.com \
    --cc=bwalton@artsci.utoronto.ca \
    --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).