From: Robert Dailey <rcdailey.lists@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Dennis Kaarsemaker <dennis@kaarsemaker.net>, Git <git@vger.kernel.org>
Subject: Re: Show all branches and ahead/behind states
Date: Fri, 15 May 2015 09:25:22 -0500 [thread overview]
Message-ID: <CAHd499Am4PFo-YRJEbQfPqtk571f4eNr_gkdy-3ATzyvBcc-jw@mail.gmail.com> (raw)
In-Reply-To: <20150514223827.GB21149@peff.net>
On Thu, May 14, 2015 at 5:38 PM, Jeff King <peff@peff.net> wrote:
> On Thu, May 14, 2015 at 01:13:15PM -0500, Robert Dailey wrote:
>
>> > git for-each-ref --format '%(HEAD) %(refname:short) %(upstream:short) %(upstream:track) %(subject)' refs/heads
>>
>> Great idea. For some reason I can't apply coloring though:
>>
>> for-each-ref --format '%(HEAD) %(refname:short) %C(bold
>> blue)%(upstream:track)%C(reset)' refs/heads
>>
>> Output:
>>
>> hotfix/4.2.3.1 %C(bold blue)[ahead 1, behind 1]%C(reset)
>
> It's spelled "%C(bold blue)" in the --pretty formats, but in
> for-each-ref, it's "%(color:bold blue)". Unifying these is one of those
> things that has been on the radar for a long time, but nobody has quite
> gotten around to it.
>
> -Peff
Thanks Jeff! That definitely fixed it. I was not able to find a
reference for this in the git docs, maybe I just overlooked it
somewhere.
As a second query, is there a way to do column alignment? For example,
I would like the ahead/behind status in one column, and the branch
names left aligned in a 2nd column. I can't simply use tabs here since
the length of column 1 may differ more greatly than a single tab
character.
I imagine there is no built in way to do this, but just curious. I'd
probably end up having to write some complicated script :-(
Thanks again you've been super helpful.
next prev parent reply other threads:[~2015-05-15 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 14:57 Show all branches and ahead/behind states Robert Dailey
2015-05-14 15:55 ` Dennis Kaarsemaker
2015-05-14 17:18 ` Robert Dailey
2015-05-14 17:29 ` Dennis Kaarsemaker
2015-05-14 18:13 ` Robert Dailey
2015-05-14 22:38 ` Jeff King
2015-05-15 14:25 ` Robert Dailey [this message]
2015-05-15 16:59 ` Jeff King
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=CAHd499Am4PFo-YRJEbQfPqtk571f4eNr_gkdy-3ATzyvBcc-jw@mail.gmail.com \
--to=rcdailey.lists@gmail.com \
--cc=dennis@kaarsemaker.net \
--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 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).