|
|
|
|
|
by _2paq
1720 days ago
|
|
Hard forks rarely get traction and are almost always lost in obscurity, unless the original project itself is abandoned. tmux isn't abandoned so I doubt this fork will end up being used by more than a handful of people. EDIT: Yup, as suspected, the author doesn't intend to keep his fork updated with upstream and I don't blame him for that. This essentially makes this fork a proof of concept, nothing more. Unless it gets merged in tmux itself, people might as well forget that this fork exists. https://github.com/csdvrx/sixel-tmux/pull/1 |
|
To be honest, Windows fangirl? guilty as charged!
But I try to keep my personal opinions separate, which is why my rants are on a separate page.
Still, you nailed it: sixel-tmux was made to try to help correct the direction that has been taken, with 6 years wasted.
I believe it's unfair that Linux users have fewer options than us Windows users, due to some people thinking sixel is "uncool".
Desperate times call for desperate measures. Publishing this fork was a last resort move, for the exact reasons you stated: forks are often lost in obscurity.
However, the situation seems to be changing: check the discussion in: https://github.com/csdvrx/sixel-tmux/pull/1 and you'll see there may be some light at the end of the tunnel!
A compile time flag is not ideal, but if at least derasterize can be added by default, so that every tmux user can have some kind of graphics in the terminal, even if said graphics are not sixels but derasterized, that would be "good enough" to me.