git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Stefan Beller <sbeller@google.com>,
	Todd Zullinger <tmz@pobox.com>, Jason Racey <jason@eluvio.com>,
	git <git@vger.kernel.org>, Paul Smith <paul@mad-scientist.net>
Subject: Re: "git branch" issue in 2.16.1
Date: Wed, 7 Feb 2018 15:08:59 -0500	[thread overview]
Message-ID: <20180207200859.GA9141@sigill.intra.peff.net> (raw)
In-Reply-To: <5A7788B0-6250-4D1F-A86D-E3155C03EF0C@gmail.com>

On Wed, Feb 07, 2018 at 06:54:23PM +0100, Lars Schneider wrote:

> > Maybe the number of branches changed since then?
> > As the pager only comes to life when the output fills
> > more than your screen. Quick workarounds:
> > * buy a bigger screen
> > * have fewer branches.
> 
> Hmmm... there might be more to it. I just noticed the
> pager behavior on macOS, too. Consider this call:
> 
> $ git diff --shortstat
> 
> This should generate at most one line of output. On Linux
> the pager is never used. On macOS the pager is always used.
> 
> I tried older versions of Git on macOS and experienced the
> same behavior.

Keep in mind that we always run the pager, since we don't know ahead of
time how much output will be generated. It's just that with certain
configurations of "less", it may exit if it sees EOF before there's a
whole screen worth of data.

This is controlled by the "-F" option. By default, Git will set LESS=FRX
in the environment if you do not already have a $LESS environment. So
some other possibilities are:

  1. You have $LESS in your environment (without "F") on one platform
     but not the other.

  2. Git was built with a different PAGER_ENV Makefile variable on one
     platform versus the other (that's what controls the baked-in LESS
     defaults).

  3. "less" somehow behaves differently on macOS. The "F" behavior is
     quite old, but possibly there's some platform-specific bug.

-Peff

  parent reply	other threads:[~2018-02-07 20:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 19:49 "git branch" issue in 2.16.1 Jason Racey
2018-02-06 19:57 ` Todd Zullinger
2018-02-06 20:05   ` Stefan Beller
2018-02-07 17:54     ` Lars Schneider
2018-02-07 18:09       ` Jason Racey
2018-02-07 19:55         ` Lars Schneider
2018-02-07 20:08       ` Jeff King [this message]
2018-02-07 20:19         ` Junio C Hamano
2018-02-07 22:20         ` Lars Schneider
2018-02-08  8:50           ` Jeff King
2018-02-08 11:13             ` Lars Schneider
2018-02-08 11:27               ` Lars Schneider
2018-02-08 16:19                 ` Kevin Daudt
2018-02-08 16:28                   ` Lars Schneider
2018-02-06 20:02 ` Paul Smith

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180207200859.GA9141@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jason@eluvio.com \
    --cc=larsxschneider@gmail.com \
    --cc=paul@mad-scientist.net \
    --cc=sbeller@google.com \
    --cc=tmz@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).