Sixel does not seem to work on Windows?

[Kreijstal]

sixel does not seem to work on windows.

[raphamorim]

Could share the version and the screenshot of what is the output?

[Kreijstal]

downloaded latest portable version from github releases

then ssh'd into some server with sixel functionality

[raphamorim]

lsix works locally for me, what is your TERM variable value?

[Kreijstal]

xterm-256color,

I am on windows 10 if it matters.

[raphamorim]

if you leave ssh and run lsix outside does it work?

[raphamorim]

tried with tmux

[Kreijstal]

Not really.
I know mintty and windows-terminal-preview handle sixel no problem, wezterm only handles sixels when done with ssh directly, but locally it fails.

[raphamorim]

@Kreijstal is this happening still?

[Kreijstal]

@Kreijstal is this happening still?

Interesting, in windows 10 it seems it whitescreened. Nothing works :), on windows 11, rio, works, except sixel of course.

with lsix I get:

Error: Your terminal does not report having sixel graphics support.

Please use a sixel capable terminal, such as xterm -ti vt340, or
ask your terminal manufacturer to add sixel support.

You may test your terminal by viewing a single image, like so:

convert foo.jpg  -geometry 800x480  sixel:-

If your terminal actually does support sixel, please file a bug
report at http://github.com/hackerb9/lsix/issues

Please mention device attribute codes: ^[[?1;0c

using timg with -ps option, I get nothing.
wezterm/wezterm#1236
smasher164/arewesixelyet#33
microsoft/terminal#1173

There is a passthrouh mode you have to activate.

[raphamorim]

Thank you for the good resources!!

I assume iterm2 protocol is working then

[Kreijstal]

iterm2 protocol seems to work...

[raphamorim]

Thank you, after your links i have a better understanding of sixel issue in windows

[Kreijstal]

might also be interesting wezterm/wezterm#6239

[Kreijstal]

someone solved it wezterm/wezterm#1236 (comment)

Btw, I got an error on windows 10 it crashes. This is unrelated to the sixel problem. I deleted already appdata/local/rio but it whitescreens

[AnonymouX47]

For what it's worth, wezterm/wezterm@4accc37 was what actually solved the issue for Wezterm as hinted at in wezterm/wezterm#6239 (comment) and tested in wezterm/wezterm#1236 (comment).

[raphamorim]

So it was the matter of updating conpty (at least is what looks like) on wezterm. Interesting though because Rio looks for the conpty instead of having it embedded

fn load_conpty() -> Option<Self> {
        type LoadedFn = unsafe extern "system" fn() -> isize;
        unsafe {
            let hmodule = LoadLibraryW(w!("conpty.dll"));
            if hmodule.is_null() {
                return None;
            }
            let create_fn = GetProcAddress(hmodule, s!("CreatePseudoConsole"))?;
            let resize_fn = GetProcAddress(hmodule, s!("ResizePseudoConsole"))?;
            let close_fn = GetProcAddress(hmodule, s!("ClosePseudoConsole"))?;

            Some(Self {
                create: mem::transmute::<LoadedFn, CreatePseudoConsoleFn>(create_fn),
                resize: mem::transmute::<LoadedFn, ResizePseudoConsoleFn>(resize_fn),
                close: mem::transmute::<LoadedFn, ClosePseudoConsoleFn>(close_fn),
            })
        }
    }

[AnonymouX47]

In short, I believe all that needs to be done is update the bundled conpty build.
I don't know if Rio currently bundles conpty (never tested on Windows) but if it doesn't, I guess that's the way to go.

[raphamorim]

Yea Rio doesn't, it uses https://github.com/microsoft/windows-rs to load the conpty.

[AnonymouX47]

Yea Rio doesn't, it uses https://github.com/microsoft/windows-rs to load the conpty.

Ah! I see.

Sorry, I posted my previous comment before seeing yours.

[AnonymouX47]

It means Rio will be stuck with whatever build comes with the windows build. 😕

[raphamorim]

No worries!

It means Rio will be stuck with whatever build comes with the windows build. 😕

Yea, that's the con side. Technically isn't that bad because this file shouldn't be updating that much but I will try to test on my windows how to update the windows conpty

[raphamorim]

oooff microsoft/vscode#224488

[AnonymouX47]

Yeah... Looks like that's the only option.

[raphamorim]

I mean could be an easy fix tbh, would need to embed the files on teletypewritter mod and update load_conpty to load the path

fn load_conpty() -> Option<Self> {
        type LoadedFn = unsafe extern "system" fn() -> isize;
        unsafe {
            let hmodule = LoadLibraryW(w!("conpty.dll"));
            if hmodule.is_null() {
                return None;
            }
            let create_fn = GetProcAddress(hmodule, s!("CreatePseudoConsole"))?;
            let resize_fn = GetProcAddress(hmodule, s!("ResizePseudoConsole"))?;
            let close_fn = GetProcAddress(hmodule, s!("ClosePseudoConsole"))?;

            Some(Self {
                create: mem::transmute::<LoadedFn, CreatePseudoConsoleFn>(create_fn),
                resize: mem::transmute::<LoadedFn, ResizePseudoConsoleFn>(resize_fn),
                close: mem::transmute::<LoadedFn, ClosePseudoConsoleFn>(close_fn),
            })
        }
    }

[raphamorim]

The trick part is to support .dll for different architectures

[AnonymouX47]

The trick part is to support .dll for different architectures

Hmm... That's true.