From: Junio C Hamano <gitster@pobox.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: git-diff should not fire up $PAGER, period!
Date: Wed, 17 Dec 2008 14:02:33 -0800 [thread overview]
Message-ID: <7viqpijw92.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <8763lixyps.fsf_-_@jidanni.org> (jidanni@jidanni.org's message of "Thu, 18 Dec 2008 05:45:35 +0800")
jidanni@jidanni.org writes:
> I mean here I am in emacs, and
>
> -*- mode: compilation; default-directory: "...coreutils/" -*-
> Compilation started at Thu Dec 18 03:15:14
> git-diff
> WARNING: terminal is not fully functional^M
> ^M- (press RETURN)
Any semi-good emacs users (let alone hackers) export PAGER=cat to be used
in compilation mode (and possibly shell mode), so this is not a problem in
practice.
I have something like this in my .emacs:
(setenv "PAGER" "cat")
I suspect (I am just a user not a hacker) this will have bad interaction
with emacs terminal emulation mode, but I do not use the mode, so it is
enough for me.
next prev parent reply other threads:[~2008-12-17 22:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 0:21 git-diff should not fire up $PAGER if there is no diff jidanni
2008-12-16 0:56 ` Jeff King
2008-12-16 6:35 ` Stefan Karpinski
2008-12-16 7:44 ` Jeff King
2008-12-16 22:43 ` Stefan Karpinski
2008-12-17 21:45 ` git-diff should not fire up $PAGER, period! jidanni
2008-12-17 22:02 ` Junio C Hamano [this message]
2008-12-17 22:04 ` Linus Torvalds
2008-12-22 3:28 ` Miles Bader
2008-12-18 3:31 ` Jeff King
2008-12-22 3:27 ` Miles Bader
2008-12-22 7:55 ` Johannes Sixt
2008-12-22 8:30 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2008-12-18 2:18 Mike Coleman
2008-12-18 2:26 ` Junio C Hamano
2008-12-18 3:22 ` Johannes Schindelin
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=7viqpijw92.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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).