From: Christoph Anton Mitterer <calestyo@scientia.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: why does git set X in LESS env var?
Date: Thu, 12 Oct 2023 00:19:40 +0200 [thread overview]
Message-ID: <3a2c362c019338ca7408b7a3bc5715b535d15b8a.camel@scientia.org> (raw)
Hey.
I recently stumbled over the problem that mouse wheel scrolling doesn't
work with (git-)delta[0], a problem[1][2], which apparently numerous
people had before me.
Numerous solutions were given in [1] and [2], for example using --mouse
as less option.
I noticed however, that this causes a somewhat different mouse
scrolling behaviour than my less usually gives me and dug a bit
further, noticing that the problem was that `X` was set in the `LESS`
env var for the less process, wrongly assuming[3] first that delta
would set it.
After delta's upstream noticed that this must be wrong, I looked
further and found that git set it since commit
0abc0260fa3419de649fcc1444e3d256a17ca6c7, which gives however no
indication why it was added.
A somewhat later commit, b3275838d969b7ecb91aae584226fccbeb046aca,
which removes `S` from being set, mentions:
> … The FRX flags actually make sense for Git (F and X because
> sometimes the output Git pipes to less is short, and R because Git
> pipes colored output).
But I still don't get from that why X would be needed?
My less manpage documents it as:
> -X or --no‐init
> Disables sending the termcap initialization and deinitialization
> strings to the terminal. This is sometimes desirable if the
> deinitialization string does something unnecessary, like clearing
> the screen.
Is it to avoid clearing the screen?
Not sure whether git should really do something here... I mean it could
add --mouse per default, but then users who don't want that would need
to work around it (and there is no negative option for --mouse, it
seems).
Oh, I should add that scrolling without `X` and without `--mouse` sees
to only work on some terminals (e.g. VTE based ones, but not xterm).
Thanks,
Chris.
[0] https://github.com/dandavison/delta/
[1] https://github.com/dandavison/delta/issues/58
[2] https://github.com/dandavison/delta/issues/630
[3] https://github.com/dandavison/delta/issues/58#issuecomment-1756542986
next reply other threads:[~2023-10-11 22:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 22:19 Christoph Anton Mitterer [this message]
2023-10-11 22:23 ` why does git set X in LESS env var? Junio C Hamano
2023-10-11 22:26 ` Christoph Anton Mitterer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a2c362c019338ca7408b7a3bc5715b535d15b8a.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).