Philip Waritschlager

One of the core designs of this extension is the usage of [vue-virtual-scroller](https://github.com/Akryum/vue-virtual-scroller/tree/next/packages/vue-virtual-scroller) which allows to scroll beyond thousands of commits without major stuttering (hopefully). The only way to meaningfully...

I'll be glad to optimize everything toward a better experience for very big repositories, I'm just not very certain on how to solve these issues

> [`-n 30`] fixes the spacing of the branch lines, but it still reserves space for all branches. this is apparently a bug, as the width doesn't seem to update...

btw I just realized the branch section can already be hidden entirely by changing removing the `--graph` from the log command

haha yes I could reproduce the zig-zagging by running the git log command in an older Debian Buster Docker container:  so you can get rid of this very particular...

Ah okay then it seems the relevant `--graph` change was introduced in git 2.40. I have fixed some of this stuff locally but I'm on vacation for a few days...

In this case it's actually as expected, the latest git version graph always looks like that in some spots. The version discrepancy was only present for that very specific other...

@Alecton4 possible, yes, but unsure how complicated. Currently this is just the way it is returned from Git itself.

I have now revised the branch rendering, and also made the branch area resizable. It's a *bit* hidden because there is no column header but after just a few moments...

@hansu oh yes there's still a min-width and a max-width in place so you don't accidentally *completely hide* the area. It should just be a few pixels though, not the...