From: Jeff King <peff@peff.net>
To: Yaakov Smith <Yaakov.Smith@wisetechglobal.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: \b character escapes in CLI usage
Date: Wed, 26 Feb 2025 03:09:02 -0500 [thread overview]
Message-ID: <20250226080902.GA29996@coredump.intra.peff.net> (raw)
In-Reply-To: <20250226073822.GA21138@coredump.intra.peff.net>
On Wed, Feb 26, 2025 at 02:38:23AM -0500, Jeff King wrote:
> I wonder if we should consider adding "U" to the default $LESS variable
> we set.
Having tried this for 5 minutes, the answer is a resounding "no". It
also treats tabs as control characters, making source code diffs rather
ugly. ;)
In modern versions of less you can get around it with:
LESS="-U --proc-tab"
or:
LESS="--PROC-BACKSPACE"
but those are new in less 632, from the last year or two. So I don't
think we can rely on it in our default variable, but people with recent
versions of less should consider setting it.
Looks like it was added for exactly this case:
https://github.com/gwsw/less/issues/335
-Peff
next prev parent reply other threads:[~2025-02-26 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 23:44 \b character escapes in CLI usage Yaakov Smith
2025-02-26 7:38 ` Jeff King
2025-02-26 8:09 ` Jeff King [this message]
2025-02-26 16:02 ` Junio C Hamano
2025-02-26 16:38 ` Kyle Lippincott
2025-02-26 22:06 ` Jeff King
2025-02-26 15:59 ` Junio C Hamano
2025-02-26 23:36 ` brian m. carlson
2025-02-26 23:55 ` Junio C Hamano
2025-02-27 0:03 ` Junio C Hamano
2025-02-27 14:06 ` General output formatting (was: Re: \b character escapes in CLI usage) Marc Branchaud
2025-02-27 17:06 ` General output formatting Junio C Hamano
2025-02-27 17:14 ` Marc Branchaud
2025-02-27 18:40 ` Junio C Hamano
2025-02-27 16:26 ` \b character escapes in CLI usage Phillip Wood
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=20250226080902.GA29996@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Yaakov.Smith@wisetechglobal.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