takaaki-kasai / git-foresta Goto Github PK

I'm trying to use this version of git-forest in combination with TamaMcGlinn/flog-forest in neovim. But the colors do not seem to work any more then.
Are the colors printed as Ansi Escape characters?
Is there anybody with experience with such a use case?

in the terminal

within neovim

It seems in your very first commit, you removed support for pretty:

    "pretty=s"                => sub {}, # ignore

This is unfortunate, as that is the reason I cannot use git-foresta inside of vim-flog. Vim-flog needs to be able to insert some special characters so that it can see where the commit hash begins, so it runs:

git-forest --pretty='format:__FSTART__%D__FSEP__%h__FSEP____DSTART__%Cblue%ad%Creset %C(yellow)[%h]%Creset %Cgreen{%an}%Creset%Cred%d%Creset %s__DEND____FEND__'

I tried re-adding like so:

-    "pretty=s"                => sub {}, # ignore
+		"pretty=s"                => \$Pretty_fmt,

but it prints garbage, probably because of some special characters being used:

$ ./git-forest --pretty='format:__FSTART__%D__FSEP__%h__FSEP____DSTART__%Cblue%ad%Creset %C(yellow)[%h]%Creset %Cgreen{%an}%Creset%Cred%d%Creset %s__DEND____FEND__'
__FSTART 1970-01-01 01:00  ○
__FSTART 1970-01-01 01:00  ◎
                           ├─┐
__FSTART 1970-01-01 01:00  │ ●
                           ├─┘
__FSTART 1970-01-01 01:00  ●
__FSTART 1970-01-01 01:00  ●
(...)

Oddly enough, even if I specify what is already the default value, it fails (commit message not shown):

$ git-forest --pretty='format:%H\t%at\t%an\t%C(reset)%C(auto)%d%C(reset)\t%s'
543537c2 1970-01-01 01:00  ○
45ffea85 1970-01-01 01:00  ◎
                           ├─┐
d481a127 1970-01-01 01:00  │ ●
                           ├─┘
a16adc14 1970-01-01 01:00  ●
7031fc34 1970-01-01 01:00  ●
(...)

I found out --date is not supported, this is a great tool that I would like to use in my work flow.

Anyway, thank you for this !

Not sure if this is expected and there's nothing you can do about this or not, but if the user has emoji in their name, then those characters don't render correctly in terminal.

The username displays in Gitlab like this:

Would it be possible to use the corner glyphs to represent the merge itself? So, instead of:

We would get:

I think this makes it clearer that the commit is a merge, rather than using a different type of circular blob, as you currently have.