Re: "git branch" issue in 2.16.1
- From
Lars Schneider <larsxschneider@gmail.com>
- Date
- Feb 7, 2018, 17:54 UTC
- Message-ID
- <5A7788B0-6250-4D1F-A86D-E3155C03EF0C@gmail.com>
- In-Reply-To
- <CAGZ79kaxf3qUyOe6R-LCgyLtwzrwhB=y767tk2qPbC_KR473ig@mail.gmail.com>
Show 34 quoted lines
> On 06 Feb 2018, at 21:05, Stefan Beller <sbeller@google.com> wrote: > > On Tue, Feb 6, 2018 at 11:57 AM, Todd Zullinger <tmz@pobox.com> wrote: >> Hi Jason, >> >> Jason Racey wrote: >>> After upgrading git from 2.16.0 to 2.16.1 (via Homebrew - >>> I’m on macOS) I noticed that the “git branch” command >>> appears to display the branch listing in something similar >>> to a vi editor - though not quite the same. I don’t know >>> the technical term for this state. You can’t actually edit >>> the output of the command, but you’re in a state where you >>> have to type “q” to exit and then the list disappears. >>> It’s very inconvenient and it doesn’t seem like it was by >>> design. I’m using zsh in iTerm2 if that helps. Thanks. >> >> In 2.16.0 `git branch --list` is sent to a pager by default. >> (Without arguments, --list is the default, so this applies >> to `git branch`). >> >> You can set pager.branch to false to disable this in the >> config, or use git --no-pager branch to do so for a single >> invocation. >> >> I can't say why you're seeing this with 2.16.1 and not >> 2.16.0, but I'm not familiar with homebrew, so perhaps >> something didn't work as intended in 2.16.0. >> > > 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.
@Jason: That might be a bug on macOS. However, I am surprised you only noticed it after upgrading from 2.16.0 to 2.16.1. Do you recall anything else you've changed?
- Lars