git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, "Phillip Wood" <phillip.wood123@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v5] help: colorize man pages
Date: Sat, 22 May 2021 16:15:43 -0500	[thread overview]
Message-ID: <60a9747fc56de_857e9208b6@natae.notmuch> (raw)
In-Reply-To: <YKjVZ28fxqGq7Baq@coredump.intra.peff.net>

Jeff King wrote:
> On Fri, May 21, 2021 at 08:17:18PM -0500, Felipe Contreras wrote:
> 
> > +	/* Add red to bold, blue to underline, and magenta to standout */
> > +	/* No visual information is lost */
> > +	setenv("LESS", "Dd+r$Du+b$Ds+m", 0);
> 
> Unlike the LESS_TERMCAP_* strategy, this completely breaks "git help"
> on my system:
> 
>   $ ./git help git
>   There is no -D option ("less --help" for help)
> 
>   $ man less | grep -A1 '^ *-D'
>          -Dxcolor or --color=xcolor
>                 [MS-DOS only] Sets the color of the text displayed.  x is a single
> 
> This is less 551-2 on Debian unstable.

I see.

Looking at their history it seems they only enabled this for non-MS-DOS
builds in 2021.

That explains why most people haven't found this yet, and are using
LESS_TERMCAP_*.

I'll revert back to LESS_TERMCAP_ and test with an ancient version of
less.

Thanks for testing.

-- 
Felipe Contreras

      reply	other threads:[~2021-05-22 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22  1:17 [PATCH v5] help: colorize man pages Felipe Contreras
2021-05-22  9:56 ` Jeff King
2021-05-22 21:15   ` Felipe Contreras [this message]

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=60a9747fc56de_857e9208b6@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=phillip.wood123@gmail.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;
as well as URLs for NNTP newsgroup(s).