From: Paul Smith <paul@mad-scientist.net>
To: Jason Racey <jason@eluvio.com>, git@vger.kernel.org
Subject: Re: "git branch" issue in 2.16.1
Date: Tue, 06 Feb 2018 15:02:25 -0500 [thread overview]
Message-ID: <1517947345.10111.103.camel@mad-scientist.net> (raw)
In-Reply-To: <2412A603-4382-4AF5-97D0-D16D5FAAFE28@eluvio.com>
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 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.
I think you mean that you're in the pager (less(1), most likely).
Many/most Git commands that can generate a large amount of output (git
log, git diff, git show, etc.) will automatically send the output to a
pager so you can scroll through it easily.
The man page for git branch says:
CONFIGURATION
pager.branch is only respected when listing branches, i.e., when --list
is used or implied. The default is to use a pager. See git-config(1).
So, if you never want to use the pager for git branch output you can
configure the pager.branch option to set it always off.
Or you can use "git branch | cat" so that stdout is not a terminal :).
prev parent reply other threads:[~2018-02-06 20:26 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
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 [this message]
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=1517947345.10111.103.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.org \
--cc=jason@eluvio.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.
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).