git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Greg KH <greg@kroah.com>,
	git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes
Date: Thu, 21 Apr 2005 08:49:31 +0200	[thread overview]
Message-ID: <20050421064931.GA31910@pasky.ji.cz> (raw)
In-Reply-To: <20050421042833.GA10934@nevyn.them.org>

Dear diary, on Thu, Apr 21, 2005 at 06:28:34AM CEST, I got a letter
where Daniel Jacobowitz <dan@debian.org> told me that...
> On Wed, Apr 20, 2005 at 09:00:44PM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Wed, 20 Apr 2005, Daniel Jacobowitz wrote:
> > > 
> > > My logic: it's a lot more intuitive to say "cg-log | less" to get
> > > paginated output than it is to say "cg-log | cat" to get unpaginated
> > > output.
> > 
> > I disagree.
> > 
> > There is _never_ any valid situation where you do "cg-log" with 
> > unpaginated output to a tty.
> > 
> > In _any_ real system you'll be getting thousands of lines of output. 
> > Possibly millions. unpaginated? What the hell are you talking about?
> 
> OK, so I'm crazy.  I must have hallucinated doing this sort of thing on
> a regular basis... :-) Examples: terminals with good scrollback,
> screen, script.  Small repositories.  Irritation at less's habit of
> using the alternate xterm buffer, whatever the technical term for that
> is.

... Plan9. But I guess you won't even have a pager there. ;-)

A little off-topic, anyone knows how to turn off that damn alternate
screen thing on the xterm level? (Or any other level which makes _all_
programs not to use it.)

More seriously, I think Linus' patch is fine; the usage in scripts is
not affected, and alternatives were suggested. When we have cg-admin, I
might even let you set per-repository git-specific PAGER (which you
could set to be even some fancy script which would parse the stuff, open
a cute window and display stuff graphically, or whatever).

Linus, ahem, could you please sign off your patch? :-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  reply	other threads:[~2005-04-21  6:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 20:56 [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Petr Baudis
2005-04-20 21:03 ` Petr Baudis
2005-04-20 21:19 ` Greg KH
2005-04-20 21:51   ` Mike Taht
2005-04-20 21:58     ` Joshua T. Corbin
2005-04-20 21:51   ` Petr Baudis
2005-04-20 21:54     ` Randy.Dunlap
2005-04-20 22:07       ` Steven Cole
2005-04-20 22:09     ` Linus Torvalds
2005-04-20 22:28       ` Petr Baudis
2005-04-20 23:04         ` Greg KH
2005-04-21  0:14         ` Linus Torvalds
2005-04-21  1:12           ` Linus Torvalds
2005-04-21  3:35             ` Daniel Jacobowitz
2005-04-21  2:45               ` Sean
2005-04-21  4:00               ` Linus Torvalds
2005-04-21  4:22                 ` Dave Jones
2005-04-21  5:08                   ` Junio C Hamano
2005-04-21  4:28                 ` Daniel Jacobowitz
2005-04-21  6:49                   ` Petr Baudis [this message]
2005-04-21 14:21                     ` Edgar Toernig
2005-04-21 16:42                       ` Petr Baudis
2005-04-24  0:09                     ` Paul Jackson
2005-04-21  5:14                 ` Randy.Dunlap
2005-04-21  4:27                   ` Sean
2005-04-21  5:29             ` Greg KH
2005-04-24  0:12             ` Paul Jackson
2005-04-21  2:48       ` Matthias Urlichs
2005-04-21 18:15         ` Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes) David A. Wheeler
2005-04-21  7:49       ` [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Ingo Molnar
2005-04-25 11:27       ` Andrew Morton
2005-04-21  2:53 ` Bryan Donlan
2005-04-21  7:36   ` Petr Baudis

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050421064931.GA31910@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=dan@debian.org \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).