From: Harald Dunkel <harri@afaics.de>
To: git@vger.kernel.org
Subject: make "git --pager/--nopager" work as intended
Date: Thu, 22 Jan 2026 10:37:49 +0100 [thread overview]
Message-ID: <87o6mm2djm.fsf@tweety.afaics.de> (raw)
Hi folks,
maybe its neurological, but the current behavior of "git -p" vs "git -P"
makes me feel uneasy. Some commands (like git diff) use a pager by default,
some ues it even without need (git branch), others don't. For every other
git command I run I have the feeling git output is not working as intended.
Setting core.pager to "cat" is not a solution. It breaks git -p.
Regards
Harri
next reply other threads:[~2026-01-22 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:37 Harald Dunkel [this message]
2026-01-22 17:17 ` make "git --pager/--nopager" work as intended Junio C Hamano
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=87o6mm2djm.fsf@tweety.afaics.de \
--to=harri@afaics.de \
--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