All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git: add -N as a short option for --no-pager
Date: Wed, 25 Apr 2018 21:30:05 +0200	[thread overview]
Message-ID: <2411e97e-bda2-869e-956e-12871761c4cc@kdbg.org> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1804250938370.4978@tvgsbejvaqbjf.bet>

Am 25.04.2018 um 09:41 schrieb Johannes Schindelin:
> Hi Hannes,
> 
> On Wed, 25 Apr 2018, Johannes Sixt wrote:
> 
>> Am 25.04.2018 um 02:05 schrieb Junio C Hamano:
>>> Johannes Sixt <j6t@kdbg.org> writes:
>>>> It is not uncommon to request that the output remains visible in
>>>> the terminal.
> 
> I ran `git log` and then hit `q`, and the latest screen contents were
> still visible in all of these scenarios:
> 
> - in a Linux VM via SSH client
> 
> - in Git Bash on Windows
> 
> - in Git CMD on Windows
> 
> Granted, this is only the latest screen, but that is usually good enough
> here.
> 
> Is anything different happening in your setups?

I have LESS=RS in my environment, because I do want that the alternate 
screen is used by the pager. Nevertheless, occasionally I want git's 
output to remain visible.

-- Hannes

  reply	other threads:[~2018-04-25 19:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 16:59 [PATCH] git: add -N as a short option for --no-pager Johannes Sixt
2018-04-25  0:05 ` Junio C Hamano
2018-04-25  5:45   ` Beat Bolli <bbolli@ewanet.ch>
2018-04-25  6:25   ` Johannes Sixt
2018-04-25  7:41     ` Johannes Schindelin
2018-04-25 19:30       ` Johannes Sixt [this message]
2018-05-01 11:41     ` Kaartic Sivaraam
2018-04-25  9:21 ` Phillip Wood
2018-04-25 19:31   ` Johannes Sixt
2018-05-01 11:25     ` Kaartic Sivaraam
2018-05-03 17:15 ` [PATCH v2] git: add -P " Johannes Sixt
2018-05-03 20:06   ` Eric Sunshine
2018-05-04  5:43     ` Junio C Hamano
2018-12-21 12:04   ` Johannes Schindelin

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=2411e97e-bda2-869e-956e-12871761c4cc@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.