all 9 comments

sorted by: hot top controversial new old
[–] 5 points 1 year ago (1 child)

This is really cool but I’m unsure why exactly the kitty/iterm image protocols are a requirement.

Is it to display the actual ‘graph’ on the left of the screen? If the terminal does not support image display does it degrade gracefully (e.g. unicode symbols) or does it just not work?

If it only works in terminal emulators with specific image support that seems a tad unfortunate for what otherwise seems a very nice fire-and-forget solution for trawling through commit logs.

  • source
  • hideshow 1 child comment
  • [–] 3 points 1 year ago (3 children)
  • [–] 1 point 1 year ago (2 children)
  • [–] 2 points 1 year ago (1 child)

    Falls into a weird niche for me - if I'm in a situation where text-only history is not good enough, I'll just use something graphical, rather than some crazy image-in-terminal solution.

    Mostly in git I use an alias I wrote/stole ages ago which displays linear history compactly.

  • source
  • hideshow 1 child comment
  • [–] 1 point 1 year ago*

    It is a handful, but git log --graph --decorate --all --full-index --color=always | less -R is what I use and I think it's great. Especially after I found the vim mode in my terminal emulator alacritty, and copying the commit hashes got really easy

  • source
  • parent
  • [–] 0 points 1 year ago

    Nice.
    I tend to use the graph made by git, but always feel like it would make my comprehension faster, if I had a properly rendered tree. But then I have been too lazy to use something like gitk.

    Looking at the repo, the code being Rust, I feel like I will give it a try the next time I need to view a graph and hopefully the interface matches my requirements.

  • source