| Thanks for being understanding. 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. |
No problem. I know maintaining forks isn't an ideal thing to do and support should ideally land upstream.
> I believe it's unfair that Linux users have fewer options than us Windows users, due to some people thinking sixel is "uncool".
I think the README page of termite pretty much sums up why getting involved in VTE, or any GNOME project for that matter, is a bad decision.
https://github.com/thestinger/termite/blob/master/README.rst...
I'm just a random spectator but perhaps your efforts might've been better spent on an independent terminal project (like Alacritty, for example) rather than trying to get features merged upstream in a GNOME project.
> 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!
Yeah, I read the entire conversation and if sixel support lands in tmux upstream, it would indeed be good news.