All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Yaakov Smith <Yaakov.Smith@wisetechglobal.com>,
	 "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: \b character escapes in CLI usage
Date: Wed, 26 Feb 2025 07:59:54 -0800	[thread overview]
Message-ID: <xmqqcyf4g0hx.fsf@gitster.g> (raw)
In-Reply-To: <20250226073822.GA21138@coredump.intra.peff.net> (Jeff King's message of "Wed, 26 Feb 2025 02:38:22 -0500")

Jeff King <peff@peff.net> writes:

> I wonder if we should consider adding "U" to the default $LESS variable
> we set.

Thanks for analyzing the "less" issue.

We should be OK if we lost the overstrike from the pager we directly
spawn and write into.  I think it is a good thing to consider,
especially because "the default $LESS variable we set" should not
affect the pager indirectly triggered by us spawning "man".

Thanks.

  parent reply	other threads:[~2025-02-26 15:59 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
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 [this message]
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=xmqqcyf4g0hx.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Yaakov.Smith@wisetechglobal.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.