Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Todd Zullinger <tmz@pobox.com>,
	 git@vger.kernel.org,  Francisco Boni <boboniboni@gmail.com>
Subject: Re: [PATCH] doc: add more examples of overriding LESS in core.pager
Date: Tue, 06 Oct 2026 09:01:19 -0700	[thread overview]
Message-ID: <xmqq33uig6nk.fsf@gitster.g> (raw)
In-Reply-To: <asQ56mv3VbiYmtwk@fruit.crustytoothpaste.net> (brian m. carlson's message of "Mon, 5 Oct 2026 23:59:39 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> On 2026-10-02 at 23:41:52, Todd Zullinger wrote:
>> +Another way to deactivate an option is prefixing `core.pager` with
>> +`LESS="RX"` to remove `-F` or `LESS=""` to override all options.
>> +This is useful if the `core.pager` command eventually runs `less` or
>> +a command which respects the `LESS` environment variable but lacks
>> +command line options to override `LESS` options.
>> ++
>> +One can specifically activate some flags for particular commands: for
>> +example, setting `pager.blame` to `less -S` enables line truncation
>> +only for `git blame`.
>
> Sure, this seems like an improvement.  I'm not very particular on the
> wording, but it's good that folks have the information that they need.

Thanks, both, for writing and reviewing.

Let me mark the topic for 'next'.

  reply	other threads:[~2026-10-06 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 12:19 pager: consider revisiting automatic LESS=FRX with custom core.pager Francisco Boni
2026-09-19 15:48 ` brian m. carlson
2026-09-19 16:37   ` Todd Zullinger
2026-10-02 23:41     ` [PATCH] doc: add more examples of overriding LESS in core.pager Todd Zullinger
2026-10-05 23:59       ` brian m. carlson
2026-10-06 16:01         ` Junio C Hamano [this message]
2026-09-19 16:52   ` pager: consider revisiting automatic LESS=FRX with custom core.pager Francisco Boni

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=xmqq33uig6nk.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=boboniboni@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    --cc=tmz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox