From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: gitzilla@gmail.com, "J. Bruce Fields" <bfields@fieldses.org>,
git@vger.kernel.org
Subject: Re: prune/prune-packed
Date: Mon, 23 Oct 2006 20:39:55 +0200 [thread overview]
Message-ID: <20061023183955.GR20017@pasky.or.cz> (raw)
In-Reply-To: <7vvembzp6y.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Mon, Oct 23, 2006 at 05:27:49AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> A Large Angry SCM <gitzilla@gmail.com> writes:
>
> > J. Bruce Fields wrote:
> >> Junio C Hamano <junkio@cox.net> writes:
> >>> I am considering the following to address irritation some people
> >>> (including me, actually) are experiencing with this change when
> >>> viewing a small (or no) diff. Any objections?
> >>
> >> So for me, if I run
> >>
> >> less -FRS file
> >>
> >> where "file" is less than a page, I see nothing happen whatsoever.
> >>
> >> At a guess, maybe it's clearing the screen, displaying the file, the
> >> restoring, all before I see anything happen?
> >
> > Junio,
> >
> > How about reverting this change? From the reports here, is causing
> > problems on a number of different distributions.
>
> Hmmm. I thought I was using gnome-terminal as well, but I
> always work in screen and did not see this problem.
>
> Sorry, but you are right and Linus is more right. How about
> doing FRSX.
I should like that solution more since I hate the alternate screen, but
I actually don't, since it should be left at the user's will whether to
use the alternate screen or not, and Git shouldn't change the default on
whim. Git is trying to be too smart here, and I think it's more annoying
to override what the user is used to than having to by default press q.
Yes, the user can always override Git by setting own $LESS, but that
means another explicit action at the user's side is required and they
don't receive any further cool flags we might stick in there later.
(BTW, I don't think this is right either. In Cogito, I do
LESS="$myflags$LESS"
unless $CG_LESS is set, in which case I do
LESS="$CG_LESS".
So people like Jens who have LESS set still get sensible behaviour from
Cogito _and_ they don't loose the ability to override Cogito's less
flags.)
BTW, I think not seeing output of paged commands is a major problem,
this should probably warrant another bugfix release.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-10-23 18:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 23:53 [ANNOUNCE] GIT 1.4.3 Junio C Hamano
2006-10-20 12:31 ` Horst H. von Brand
2006-10-20 13:26 ` Peter Eriksen
2006-10-20 23:35 ` Junio C Hamano
2006-10-21 0:14 ` Linus Torvalds
2006-10-21 0:22 ` Petr Baudis
2006-10-21 0:31 ` Linus Torvalds
2006-10-21 9:53 ` Andreas Schwab
2006-10-22 21:09 ` Anders Larsen
2006-10-21 2:12 ` Al Viro
2006-10-21 5:29 ` Junio C Hamano
2006-10-21 5:40 ` Al Viro
2006-10-21 14:29 ` Rene Scharfe
2006-10-21 0:47 ` Nicolas Pitre
2006-10-23 0:53 ` prune/prune-packed J. Bruce Fields
2006-10-23 1:26 ` prune/prune-packed A Large Angry SCM
2006-10-23 2:36 ` [ANNOUNCE] GIT 1.4.3 J. Bruce Fields
2006-10-23 3:27 ` prune/prune-packed Junio C Hamano
2006-10-23 18:39 ` Petr Baudis [this message]
2006-10-27 21:19 ` prune/prune-packed Jon Loeliger
2006-10-27 21:55 ` prune/prune-packed Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-10-22 3:59 prune/prune-packed J. Bruce Fields
2006-10-22 4:59 ` prune/prune-packed Junio C Hamano
2006-10-22 23:14 ` prune/prune-packed J. Bruce Fields
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=20061023183955.GR20017@pasky.or.cz \
--to=pasky@suse.cz \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--cc=junkio@cox.net \
/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).