Re: text-based tree visualizer

From: Jan Engelhardt <jengelh@computergmbh.de>
Date: Mar 17, 2008, 16:27 UTC
Message-ID: <Pine.LNX.4.64.0803171716470.18817@fbirervta.pbzchgretzou.qr>
In-Reply-To: <46dff0320803170640g52411015g7bbe315df2b0bb56@mail.gmail.com>

On Mar 17 2008 21:40, Ping Yin wrote:

Show 21 quoted lines

>>
>>  I spent the last two days writing a text-based tree visualizer;
>>  gitk is really convenient, but unfortunately it needs an X display,
>>  tigs tree view left me unimpressed, and I actually wanted a tool
>>  that does not read all commits in like gitk/tig do, but just gives me
>>  the treeview.
>>
>Here is my view
>║ ║ ║ ╟ Merge branch 'jk/portable'
>║ ║ ║ ╠═╗
>║ ║ ║ ╟ ║ Merge branch 'py/submodule'
>║ ║ ║ ╠═╬═╗
>║ ║ ║ ╟ ║ ║ Merge branch 'db/diff-to-fp'
>║ ║ ║ ╠═╬═╬═╗
>║ ║ ║ ╟ ║ ║ ║ Merge branch 'cc/help'
>║ ║ ║ ╠═╬═╬═╬═╗
>║ ║ ║ ╟ ║ ║ ║ ║ shortlog: do not require to
>║ ║ ║ ╟ ║ ║ ║ ║ Merge branch 'maint'
>║ ║ ║ ╠═╬═╬═╬═╬═╗
>
>It seems messed up.

It looks pretty normal. Once a vine-branch (║) branches off [a merge is done in history], it stays in its column for the entire time. It is different from gitk which moves branches to the left/right so that there are less crossovers (╬) in gitk. But in git-forest that is intentional. Also note that ╬ is not a "go-everywhere" intersection -- see the top of the git-forest script and/or try --style=3 or =0 option to make it apparent:

│ ├ │ │ │ │ │ │ │ │ Merge branch 'jk/portable' │ ╞═╪═╪═╪═╪═╪═╪═╕ │ │ │ ├ │ │ │ │ │ │ │ │ │ Merge branch 'py/submodule' │ ╞═╪═╪═╪═╪═╪═╪═╪═╕ │ │ │ ├ │ │ │ │ │ │ │ │ │ │ Merge branch 'db/diff-to-fp' │ ╞═╪═╪═╪═╪═╪═╪═╪═╪═╕ │ │ │ ├ │ │ │ │ │ │ │ │ │ │ │ Merge branch 'cc/help' │ ╞═╪═╪═╪═╪═╪═╪═╪═╪═╪═╕ │ │ │ ├ │ │ │ │ │ │ │ │ │ │ │ │ shortlog: do not require to run from inside a git re

Or was it something else you meant to describe with being messed up?