From: Raphael <raphael@pdev.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: BUG: %+ format placeholder and colors
Date: Wed, 23 Mar 2022 19:12:03 +0100 [thread overview]
Message-ID: <e8417ad5-f9f2-c1de-75f6-45be49f0011b@pdev.de> (raw)
In-Reply-To: <220323.86wnglnzrq.gmgdl@evledraar.gmail.com>
> At least for me a screenshot & a link to a repo you expect to run this
> on would really help, since the output is very different depending on
> branch topology, ref names etc.
I believe the branch topology is not relevant to reproduce this bug, it
happens in my small demo repo with two commits as well as big repos.
I uploaded a screenshot at https://qu.ax/Mzuv.png
The key is that lines starting with the pipe symbol should have their
text printed in red, which does not happen.
The general idea is to highlight when a commit has refnames, which I
want to print in an optional second line and colorized. The latter seems
not possible currently.
The exact command used was:
git log --pretty=format:'%h %s%Cred%+d test' --graph
next prev parent reply other threads:[~2022-03-23 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 22:38 Pretty format color bug Raphael Bauer
2022-02-21 23:29 ` Ævar Arnfjörð Bjarmason
2022-02-22 0:15 ` Raphael Bauer
2022-03-22 23:42 ` BUG: %+ format placeholder and colors Raphael Bauer
2022-03-23 2:49 ` Ævar Arnfjörð Bjarmason
2022-03-23 18:12 ` Raphael [this message]
2022-04-05 15:45 ` [PATCH] pretty format: fix colors on %+ placeholder newline Raphael Bauer
2022-04-06 21:16 ` Junio C Hamano
2022-04-08 13:18 ` Raphael
2022-04-08 15:14 ` Ævar Arnfjörð Bjarmason
2022-04-08 23:40 ` Junio C Hamano
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=e8417ad5-f9f2-c1de-75f6-45be49f0011b@pdev.de \
--to=raphael@pdev.de \
--cc=avarab@gmail.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;
as well as URLs for NNTP newsgroup(s).