[speeddemon]

You're saying you're "reading between the lines", that reads to me like an emotional statement, not a technical one. Please let's focus on the technical issues at hand and what has actually been said, not on what we think someone might be saying.

>tell me precisely what doesn't work, in your own words.

I already explained it, I've used sixel in Xterm and Foot and I don't like it, the restriction to paletted images makes everything look bad. Also, changing the font size breaks the images. Also, the protocol is still terrible on bandwidth, if you use it to try to transmit 1080p video over ssh (as someone is bound to do) then you will encounter the same bandwidth issues. Again please read this issue if you want to know more about my stance, I agree with everything it's saying: https://gitlab.freedesktop.org/terminal-wg/specifications/-/...

So sixel-tmux is not going to help me, sorry. It may even make things worse for me if apps are trying to use it when I don't want it. If you want some more suggestions on what to do to help, I can give those. But you're also welcome to not listen to me if you disagree. Maybe you have to accept that I am just not in your target audience, but that's no reason to accuse other maintainers of trying to hold me hostage.

Edit: I said earlier that I think it would be a good goal to support the various image protocols, I would be happy to use this if eventually an image protocol was added there that wasn't seriously flawed. But the apps and terminal emulators will still have to be changed to support that, so supporting sixel doesn't really help towards that goal at all, and in some ways it impedes it because those projects might be expected to maintain that as a backwards compatibility option. That's what I meant earlier, I think you may be approaching this problem from the wrong angle.

[csdvrx]

> the restriction to paletted images makes everything look bad

Not with 16 million colors. That's what 24 bit color mean (2^16) also called "truecolor" mode

> Also, changing the font size breaks the images.

Not on mintty. I can change the font size up and down, it even resizes the sixels in proportion so the images remain aligned to the text in a pixel-perfect way.

It's a terminal problem. You are using bad terminals. I grant you that xterm is the least worst option on linux, but do yourself a favor and try mintty on Windows.

> Also, the protocol is still terrible on bandwidth

Are you using telnet on remote hosts? Unless you do that, with ssh, compression means I can stream video (!!!) just like on local hosts (where bandwith is not an issue)

> It may even make things worse for me if apps are trying to use it when I don't want it.

In the future, sixel-tmux will intercept sixels live and rewrite them into other format, like iTerm or kitty.

How is that making things harder for you?

If you really don't want sixel even if your terminal supports them, use the appropriate terminfo and you will see nothing.

> seriously flawed

You have yet to tell me the flaws in your own words, flaws that are not due to a given terminal.

Try to use sixel to play videos in mintty, with 24 bit support so palettes aren't a problem. Then try tweaking the font size (why not!), notice how it remains a perfect user experience, then we'll talk again.

For now, all I see is FUD.

[speeddemon]

>Not with 16 million colors. That's what 24 bit color mean (2^16) also called "truecolor" mode

>Try to use sixel to play videos in mintty, with 24 bit support so palettes aren't a problem.

You are confusing sixel with the iTerm image protocol which is different. Sixel is a really old and outdated, inefficient protocol that only supports uncompressed 6-bit paletted images. It would be best if we could just stop talking about sixel altogether, because this is not even what you're referring to anymore. I'm actually concerned that you're conflating these two, it would also best if you could be clear about this in terms of your project so it's not confusing as to what your project supports. Maybe the name should change from sixel-tmux at some point?

SSH compression is not going to be better than the image's native compression, you really don't want to rely on that to compress your images when we already have dozens of other better ways to transmit video.

>Not on mintty. I can change the font size up and down, it even resizes the sixels in proportion so the images remain aligned to the text in a pixel-perfect way.

I'd love to look into how that's accomplished but I can't use mintty because I use a Mac, sorry. I'm also not really interested in trying to mess with mingw just to get this set up.

This isn't FUD either, you're saying the terminals are bad, well, there is no terminal I can use that works correctly, I suggested to help out fixing the terminals if you know how and you basically said no. So what am I supposed to do? Part of making a good protocol is making one that is easy for the apps and terminal emulators to implement correctly, if that doesn't exist, then like I said you have to go back to square one. Adding this support to tmux is useful in some cases, but it still isn't going to help with getting the terminals to implement this right.

>In the future, sixel-tmux will intercept sixels live and rewrite them into other format, like iTerm or kitty.

This is a good idea, please do this instead of trying to get other terminals to adopt Sixel when they are just going to have to replace it down the line anyway.