git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: piped to a pager (was: how to speed up "git log"?)
Date: Sun, 18 Feb 2007 01:09:26 +0100	[thread overview]
Message-ID: <200702180109.26412.bruno@clisp.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0702180019040.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:
> you can blame the person calling git log and waiting until it 
> finishes. See the list archives for reasons why.
... and earlier:
> Usually the output of git-log -- even with pathname 
> filtering -- starts almost instantaneous, and is piped to your pager.

The pager ('less') in a console is not a good solution for everone:
  - People used to GUI editors (kate, nedit, ...) miss a scroll bar for
    navigation. You can't use kate or nedit as a pager.
  - PAGER="vi -" also reads all input before it displays anything.
  - PAGER="xless" likewise.
  - In Emacs shell-mode, with PAGER="", you see the output as it is produced,
    but it's disturbing to work in a buffer which is growing, where the scrollbar
    continues to change its position.

It's OK for many people, but not for everyone.

Bruno

  reply	other threads:[~2007-02-18  0:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11 11:52 how to speed up "git log"? Bruno Haible
2007-02-11 16:49 ` Johannes Schindelin
2007-02-11 23:00   ` Shawn O. Pearce
2007-02-11 23:08     ` Johannes Schindelin
2007-02-11 23:41   ` Bruno Haible
2007-02-11 23:46     ` Shawn O. Pearce
2007-02-11 23:56     ` Johannes Schindelin
2007-02-11 23:59     ` Robin Rosenberg
2007-02-12  2:02       ` Bruno Haible
2007-02-12 11:19         ` Johannes Schindelin
2007-02-12  4:08       ` Junio C Hamano
2007-02-12  6:06         ` Shawn O. Pearce
2007-02-12  6:11           ` Junio C Hamano
2007-02-12  6:22             ` Shawn O. Pearce
2007-02-12  6:28               ` Shawn O. Pearce
2007-02-12  4:20     ` Linus Torvalds
2007-02-12 11:27       ` Bruno Haible
     [not found] ` <20070211152840.GA2781@steel.home>
2007-02-11 23:52   ` Bruno Haible
2007-02-17 19:19   ` Bruno Haible
2007-02-17 23:20     ` Johannes Schindelin
2007-02-18  0:09       ` Bruno Haible [this message]
2007-02-18  0:10         ` piped to a pager (was: how to speed up "git log"?) Johannes Schindelin
2007-02-18  6:33     ` how to speed up "git log"? Shawn O. Pearce

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=200702180109.26412.bruno@clisp.org \
    --to=bruno@clisp.org \
    --cc=Johannes.Schindelin@gmx.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;
as well as URLs for NNTP newsgroup(s).