From: Linus Torvalds <torvalds@osdl.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] "git --less cmd" to page anywhere
Date: Tue, 6 Jun 2006 20:21:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606062011030.5498@g5.osdl.org> (raw)
In-Reply-To: <46a038f90606061929i68073677i686a3c1934ed64b1@mail.gmail.com>
On Wed, 7 Jun 2006, Martin Langhoff wrote:
>
> Why is it not a good default? Unless I expect it to be shorter than
> the terminal, I always tack "| less" after it. Except when I tack ">
> foo.patch" and then the auto-pager knows what to do anyway.
I often tack "| less" after it in some situations, but in other situations
I _never_ do.
I often use "git diff" as a way to see that my tree is clean. Sure, I
could do "git status", but if it's not clean, it's usually something
small, so I want to know what I changed last. At that point, a default
pager would be very annoying.
The "more" behaviour (which only paginates unto the end) might work for
me (ie the "git diff" auto-pager would act like "more" or "less -EX")
I dunno.
Linus
prev parent reply other threads:[~2006-06-07 3:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 21:19 [PATCH] Support for configurable git command aliases (v2) Petr Baudis
2006-06-04 21:20 ` Petr Baudis
2006-06-04 22:11 ` Martin Mares
2006-06-04 22:19 ` Petr Baudis
2006-06-04 22:38 ` Junio C Hamano
2006-06-04 23:31 ` Linus Torvalds
2006-06-06 23:58 ` [PATCH/RFC] "git --less cmd" to page anywhere Junio C Hamano
2006-06-07 0:05 ` Linus Torvalds
2006-06-07 0:08 ` Petr Baudis
2006-06-07 0:12 ` Linus Torvalds
2006-06-07 2:29 ` Martin Langhoff
2006-06-07 3:21 ` Linus Torvalds [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=Pine.LNX.4.64.0606062011030.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=martin.langhoff@gmail.com \
--cc=pasky@suse.cz \
/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).