All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mark Nudelman <markn@greenwoodsoftware.com>
Cc: Bill Lear <rael@zopyra.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [Announce] GIT v1.5.0-rc2
Date: Wed, 24 Jan 2007 10:18:52 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701241012030.3606@woody.linux-foundation.org> (raw)
In-Reply-To: <45B79D68.6040200@greenwoodsoftware.com>



On Wed, 24 Jan 2007, Mark Nudelman wrote:
>
> The first issue that you mention (that we move to the bottom of the screen
> before printing the first line) is behavior that has always existed in less.
>
> BTW, this issue is documented as enhancement request #112 at
> http://www.greenwoodsoftware.com/less/bugs.html.

I don't dispute that the "move to the bottom of the screen" is probably a 
good feature in general, but it is _not_ a good feature when -F is in 
effect (similar to the init/exit sequence being a horrible thing to do 
when -F is in effect).

So the problem is that it basically makes -F largely useless.. The whole 
_point_ of anybody using -F is that it turns off the "pager" feature for 
small output that fits on a page, wouldn't you say?

(The reason the init/exit sequence doesn't mix with -F is that many 
terminal descriptions basically have a "switch to secondary screen" for 
init, and "switch back" for exit, which means that together with -F, small 
output simply won't be shown at all - or perhaps it just flickers too 
quickly for the user to see it).

So this really is only a -F issue.

Now, for the init/exit sequence, at least we have -X to turn that off (and 
git does indeed default to using "FRSX" if the user doesn't have any LESS 
environment variable set), so perhaps the "move to end of screen" could 
also get another flag? That way it would be something that users can 
control - but see above on why I pretty much guarantee that anybody who 
uses -F would want to use the new flag too.

> Your second issue is definitely a bug.  Less's handling of -F and eof in
> general is indeed rather baroque and confusing, and probably needs a complete
> revision.  Some of the complexity comes from being portable to many (not
> necessarily Unix-like) systems.

Yeah, I tried to look at the sources, and ran awya screaming ;)

		Linus

  reply	other threads:[~2007-01-24 18:20 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  8:56 [Announce] GIT v1.5.0-rc2 Junio C Hamano
2007-01-21  9:40 ` Jakub Narebski
2007-01-21 10:52   ` Junio C Hamano
2007-01-21 11:08   ` Johannes Schindelin
2007-01-23 18:12     ` Bill Lear
2007-01-23 19:12       ` Johannes Schindelin
2007-01-23 20:12         ` Bill Lear
2007-01-23 20:22           ` Uwe Kleine-König
2007-01-23 20:31             ` Bill Lear
2007-01-24 10:06               ` Uwe Kleine-König
2007-01-23 20:22           ` Johannes Schindelin
2007-01-23 21:09           ` Peter Baumann
2007-01-23 21:54             ` Bill Lear
2007-01-23 20:32       ` Linus Torvalds
2007-01-24 17:54         ` Mark Nudelman
2007-01-24 18:18           ` Linus Torvalds [this message]
2007-01-24 19:21         ` Linus Torvalds
2007-01-24 23:23           ` Junio C Hamano
2007-03-27  0:07         ` Mark Nudelman
2007-01-21 11:20 ` Junio C Hamano
2007-01-21 13:42   ` Bill Lear
2007-01-21 13:52     ` Bill Lear
2007-01-21 15:02       ` Michael
2007-01-21 15:02         ` Michael
2007-01-21 21:26       ` Johannes Schindelin
2007-01-21 21:33         ` Jakub Narebski
2007-01-21 21:33           ` Jakub Narebski
2007-01-21 22:01           ` Johannes Schindelin
2007-01-21 22:24             ` Jakub Narebski
2007-01-21 22:24               ` Jakub Narebski
2007-01-21 13:43   ` Willy Tarreau
2007-01-21 15:06     ` Jakub Narebski
2007-01-21 15:06       ` Jakub Narebski
2007-01-21 18:58     ` Junio C Hamano
2007-01-21 19:49       ` H. Peter Anvin
2007-01-22 17:23         ` Nicolas Pitre
2007-01-21 20:01       ` Horst H. von Brand
2007-01-22  1:27         ` Junio C Hamano
2007-01-21 19:46   ` Horst H. von Brand
2007-01-21 20:51     ` Junio C Hamano
2007-01-21 21:55   ` Johannes Schindelin
2007-01-21 22:45     ` Jakub Narebski
2007-01-21 22:45       ` Jakub Narebski
2007-01-21 22:52       ` Johannes Schindelin
2007-01-21 23:08         ` Jakub Narebski
2007-01-21 23:13           ` Johannes Schindelin
2007-01-21 23:36             ` Jakub Narebski
2007-01-22  0:55     ` Junio C Hamano
2007-01-22  6:25     ` Junio C Hamano
2007-01-23  6:47     ` [PATCH 1/2] Refactor the pack header reading function out of receive-pack.c Junio C Hamano
2007-01-23  6:47     ` [PATCH 2/2] Allow fetch-pack to decide keeping the fetched pack without exploding Junio C Hamano
2007-01-23 10:32       ` Johannes Schindelin
2007-01-23 10:55         ` Jakub Narebski
2007-01-23 11:07           ` code movements in diffs, was " Johannes Schindelin
2007-01-23 16:01         ` Nicolas Pitre
2007-01-25  1:14           ` [PATCH] fetch-pack: remove --keep-auto and make it the default Junio C Hamano
2007-01-25  8:23             ` Johannes Schindelin
2007-01-25 21:32               ` Junio C Hamano
2007-01-25 23:46                 ` Johannes Schindelin
2007-01-26  3:05                 ` Junio C Hamano
2007-01-26  3:30                   ` [PATCH] Allow non-developer to clone, checkout and fetch easier Junio C Hamano
2007-01-26 14:20                     ` Alex Riesen
2007-01-26  8:37                 ` [PATCH] fetch-pack: remove --keep-auto and make it the default Johannes Sixt
2007-01-25  1:14           ` [PATCH] Consolidate {receive,fetch}.unpackLimit Junio C Hamano
2007-01-25  3:32             ` Nicolas Pitre
2007-01-25  5:14             ` Shawn O. Pearce
2007-01-23 16:15         ` [PATCH 2/2] Allow fetch-pack to decide keeping the fetched pack without exploding Linus Torvalds
2007-01-23 16:28           ` David Kågedal
2007-01-23 16:43             ` Johannes Schindelin
2007-01-23 17:22               ` Jakub Narebski
2007-01-22 18:08   ` [Announce] GIT v1.5.0-rc2 Carl Worth
2007-01-22 19:28     ` Junio C Hamano
2007-01-23  1:01       ` Carl Worth
2007-01-22 18:22   ` Jakub Narebski
2007-01-22 18:22     ` Jakub Narebski
2007-01-22 18:46     ` Junio C Hamano

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.0701241012030.3606@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=markn@greenwoodsoftware.com \
    --cc=rael@zopyra.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.