Re: "git branch" issue in 2.16.1

> On 08 Feb 2018, at 17:19, Kevin Daudt wrote: > > On Thu, Feb 08, 2018 at 12:27:07PM +0100, Lars Schneider wrote: >> >>> On 08 Feb 2018, at 12:13, Lars Schneider wrote: >>> >>> On 08 Feb 2018, at 09:50, Jeff King wrote:

Re: "git branch" issue in 2.16.1

On Thu, Feb 08, 2018 at 12:27:07PM +0100, Lars Schneider wrote: > > > On 08 Feb 2018, at 12:13, Lars Schneider wrote: > > > > > >> On 08 Feb 2018, at 09:50, Jeff King wrote: > >> > >> On Wed, Feb 07, 2018 at 11:20:08PM +0100, Lars Schneider wrote: >

Re: "git branch" issue in 2.16.1

> On 08 Feb 2018, at 12:13, Lars Schneider wrote: > > >> On 08 Feb 2018, at 09:50, Jeff King wrote: >> >> On Wed, Feb 07, 2018 at 11:20:08PM +0100, Lars Schneider wrote: >> 1. You have $LESS in your environment (without "F") on one platform

Re: "git branch" issue in 2.16.1

> On 08 Feb 2018, at 09:50, Jeff King wrote: > > On Wed, Feb 07, 2018 at 11:20:08PM +0100, Lars Schneider wrote: > >>> 1. You have $LESS in your environment (without "F") on one platform >>>but not the other. >> >> I think that's it. On my system LESS is defined to "-R". >>

Re: "git branch" issue in 2.16.1

On Wed, Feb 07, 2018 at 11:20:08PM +0100, Lars Schneider wrote: > > 1. You have $LESS in your environment (without "F") on one platform > > but not the other. > > I think that's it. On my system LESS is defined to "-R". > > This opens the pager: > > $ echo "TEST" | less > > This

Re: "git branch" issue in 2.16.1

> On 07 Feb 2018, at 21:08, Jeff King wrote: > > 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: >>> *

Re: "git branch" issue in 2.16.1

Jeff King writes: > 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

Re: "git branch" issue in 2.16.1

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

Re: "git branch" issue in 2.16.1

> On 07 Feb 2018, at 19:09, Jason Racey wrote: > > Hi Lars, > > Here’s what I’m certain of: > > 1. Just set up a new MacBook Pro at work. Git version 2.16.1 installed via > Homebrew. “git branch” command always displays the list of branches in the > less pager, regardless

Re: "git branch" issue in 2.16.1

Hi Lars, Here’s what I’m certain of: 1. Just set up a new MacBook Pro at work. Git version 2.16.1 installed via Homebrew. “git branch” command always displays the list of branches in the less pager, regardless of number of branches or screen size. I’ve never seen this happen before. 2.

Re: "git branch" issue in 2.16.1

> On 06 Feb 2018, at 21:05, Stefan Beller wrote: > > On Tue, Feb 6, 2018 at 11:57 AM, Todd Zullinger 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”

Re: "git branch" issue in 2.16.1

On Tue, 2018-02-06 at 11:49 -0800, 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

Re: "git branch" issue in 2.16.1

On Tue, Feb 6, 2018 at 11:57 AM, Todd Zullinger 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

Re: "git branch" issue in 2.16.1

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