From: Christoph Anton Mitterer <calestyo@scientia.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: why does git set X in LESS env var?
Date: Thu, 12 Oct 2023 00:26:52 +0200 [thread overview]
Message-ID: <0c10c4b95f2a947a5d569a2c3d51fcb02b35e81d.camel@scientia.org> (raw)
In-Reply-To: <xmqqa5sokdd3.fsf@gitster.g>
On Wed, 2023-10-11 at 15:23 -0700, Junio C Hamano wrote:
> I think that was the reason we added it back in 2005. In any case,
> asking "why" is not a useful use of anybody's time, because it is
> very unlikely to change in the official version we ship, and because
> it is so easy for any individual who does not like it to drop by
> exporting the $LESS environment variable.
Well the other commit I've mentioned kinda read as if it was thought
that either X or both F and X were needed for the effect to exit less
immediately if the output is too short ("F and X because
> sometimes the output Git pipes to less is short").
So I thought maybe that was intended, and the no-clear was just a side-
effect no one ever really thought about.
Anyway, thanks,
Chris.
next prev parent reply other threads:[~2023-10-11 22:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 22:19 why does git set X in LESS env var? Christoph Anton Mitterer
2023-10-11 22:23 ` Junio C Hamano
2023-10-11 22:26 ` Christoph Anton Mitterer [this message]
2023-10-11 22:51 ` Dragan Simic
2023-10-11 23:16 ` Christoph Anton Mitterer
2023-10-11 23:29 ` Dragan Simic
2023-10-11 23:43 ` Christoph Anton Mitterer
2023-10-12 0:06 ` Dragan Simic
2023-10-12 0:22 ` Christoph Anton Mitterer
2023-10-12 0:31 ` Dragan Simic
2023-10-12 1:39 ` Christoph Anton Mitterer
2023-10-12 5:46 ` Dragan Simic
2023-10-12 20:23 ` Christoph Anton Mitterer
2023-10-12 21:15 ` Dragan Simic
2023-10-12 21:48 ` Christoph Anton Mitterer
2023-10-12 22:36 ` Dragan Simic
2023-10-12 23:06 ` Christoph Anton Mitterer
2023-10-13 4:43 ` Dragan Simic
2023-10-13 13:45 ` Christoph Anton Mitterer
2023-10-13 15:00 ` Dragan Simic
2023-10-12 0:04 ` Jeff King
2023-10-12 0:16 ` Dragan Simic
2023-10-12 1:39 ` Junio C Hamano
2023-10-12 5:30 ` Dragan Simic
2023-10-12 16:19 ` Junio C Hamano
2023-10-13 20:12 ` Dragan Simic
[not found] ` <cfbe174f-23ac-4a35-8db4-66bdfdfdc14e@gmail.com>
2023-11-02 6:01 ` Thomas Guyot
2023-11-02 6:14 ` Dragan Simic
2023-11-02 6:48 ` Dragan Simic
2023-11-02 13:19 ` Thomas Guyot
2023-11-02 14:19 ` Dragan Simic
2023-11-03 11:47 ` Thomas Guyot
2023-11-03 15:28 ` Andy Koppe
2023-11-03 18:38 ` Dragan Simic
2023-11-03 18:22 ` Dragan Simic
2023-11-06 3:47 ` Dragan Simic
2024-03-21 15:53 ` Dragan Simic
2023-10-12 3:54 ` Christoph Anton Mitterer
2023-10-12 5:57 ` Dragan Simic
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=0c10c4b95f2a947a5d569a2c3d51fcb02b35e81d.camel@scientia.org \
--to=calestyo@scientia.org \
--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.