Wez Furlong
Wez Furlong
it was never an option before, and bringing it back is not simple. It was a bug with clustering and rendering that was outright wrong; it isn't the behavior that...
The Windows ConPTY layer might be interfering with this. If you use `wezterm ssh` to connect directly to the remote host, I would expect this to work. Could you try...
We're waiting on some combination of: https://github.com/microsoft/terminal/issues/1173 https://github.com/microsoft/terminal/issues/448 before this will work directly on ConPTY
@ykhan21 wezterm *does* support sixel graphics. It's conpty in the middle that can mess things up
The workaround that I suggest is using `wezterm ssh` to get directly into eg: a WSL environment or a remote linux environment
No, conpty, which is intimately tied to native console program output on windows, does not support sixels. To use sixel, you need to avoid conpty. Learn more about conpty: https://wezfurlong.org/wezterm/what-is-a-terminal.html#windows-and-conpty...
Thank you for confirming that it works!
I'll accept a patch for this. I don't use arch. I do find it irritating that there doesn't seem be a way to handle PRs for this sort of package...
I think this has now been resolved, please try and let me know
Try with a different cwd in case there is something strange about that? eg: `wezterm start --cwd c:/` or by setting https://wezfurlong.org/wezterm/config/lua/config/default_cwd.html differently in the configuration. What might be strange...