From: Jeff King <peff@peff.net>
To: Frans Klaver <fransklaver@gmail.com>
Cc: Alexey Shumkin <Alex.Crezoff@gmail.com>, git@vger.kernel.org
Subject: Re: BUG. Git config pager when --edit
Date: Mon, 7 Nov 2011 11:42:50 -0500 [thread overview]
Message-ID: <20111107164250.GC27055@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH6sp9Ox+6p4RkjCZ0j3tXG9F4u7SPuwbSrOWmLSXic9DxSKiQ@mail.gmail.com>
On Mon, Nov 07, 2011 at 02:43:41PM +0100, Frans Klaver wrote:
> > As far as my config is large enough to be paged I set pager.config=less
> > setting. But since that moment when I run
> > $ git config --edit
> > I get
> > Vim: Warning: Output is not to a terminal
> > And some messed config output
> >
> > The same happens if to run
> > $ vim .git/config | less
>
> So git is trying to tell vim to pipe its output to less. vim can't do
> that because it needs a terminal, as it's the only way vim is usable.
>
> Should pager.config then only be used with --list?
Yes, but it can't, because it is not the config command, but the git
wrapper that respects "pager.config". We have similar issues with
setting "pager.tag" (you want it for listing, but not for tag creation)
and others.
I should probably polish and submit the patch here:
http://thread.gmane.org/gmane.comp.version-control.git/182238/focus=182475
-Peff
next prev parent reply other threads:[~2011-11-07 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 13:26 BUG. Git config pager when --edit Alexey Shumkin
2011-11-07 13:43 ` Frans Klaver
2011-11-07 16:42 ` Jeff King [this message]
2011-11-07 17:02 ` Junio C Hamano
2011-11-07 17:18 ` Jeff King
2011-11-07 20:45 ` Frans Klaver
2011-11-07 14:54 ` how to merge sub directory or file? Emily
2011-11-07 15:37 ` Konstantin Khomoutov
2011-11-08 7:08 ` Emily Ren
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=20111107164250.GC27055@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Alex.Crezoff@gmail.com \
--cc=fransklaver@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).