git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Diggory Hardy <diggory.hardy@gmail.com>
To: git@vger.kernel.org
Subject: Re: LESS env var and a pager
Date: Fri, 31 Jul 2009 14:25:41 +0200	[thread overview]
Message-ID: <31718a220907310525v681eb2c4l53c41fdec32f3f72@mail.gmail.com> (raw)
In-Reply-To: <31718a220907300010t136885c6ldc2ea362f9c6e33@mail.gmail.com>

Unfortunately using F without X results in output no longer than one
screen not being displayed, since less immediately exits and anything
less would display is immediately cleared from the screen (so it just
looks like the git command had no output).

I looked through less's man page and didn't find any solution other
than also not specifying F, which is not so desirable since it's
always necessary to press 'q' to exit less and previous output is not
visible on the terminal.

[So don't follow my first suggestion.]

On 30/07/2009, Diggory Hardy <diggory.hardy@gmail.com> wrote:
> I was recently trying to work out why when git's output is piped
> through a pager, it doesn't use the alternate screen buffer:
> https://bugs.kde.org/show_bug.cgi?id=201899
>
> Conclusion: removing the X option from the LESS environ var produced
> the results I wanted (allow mouse-wheel scrolling, output is hidden
> after closing the pager).
> One relevent post I found:
> http://article.gmane.org/gmane.comp.version-control.git/29565/match=less+frsx
>
> So maybe it'd make sense to change this in pager.c to:
> setenv("LESS", "FRS", 0);
> (or even just FR:)
> setenv("LESS", "FR", 0);
>
> Just a suggestion of what seems preferable to me.
>

      reply	other threads:[~2009-07-31 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  7:10 LESS env var and a pager Diggory Hardy
2009-07-31 12:25 ` Diggory Hardy [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=31718a220907310525v681eb2c4l53c41fdec32f3f72@mail.gmail.com \
    --to=diggory.hardy@gmail.com \
    --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).