-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Console now supports Sixel #33
Comments
Just to be clear, that PR adds Sixel support to conhost (that's the old Windows console). It's not available in Windows Terminal yet. |
Whoops, my bad! In that case however, does the Windows Console section need updating then? EDIT: I went ahead and updated the title + initial post to reflect the actual changes I mentioned. |
I'm not sure what exactly the criteria are for claiming sixel support on this site. Right now we've got a PR committed, and technically anyone could download the nightly build and use it if they really wanted to, but it'll be some time before it makes its way into the inbox Windows console which most users have access to. So for now you may want to hold off on claiming anything, or at least include a massive disclaimer clarifying that it's not generally available (and it's possible it might never be). |
FYI, with PRs microsoft/terminal/#17581 and microsoft/terminal/#17510 having been merged now, we've got Sixel support in Windows Terminal too. As with conhost, it's still only accessible in the nightly build, but my understanding is that they are planning for a preview release around the end of the month. |
the nightly release is there, so we wait till stable releasse |
I have it working in Windows Terminal Preview. |
Yes, as of Windows Terminal Preview 1.22, sixel support is now included. |
1.22 is still pre-release, the current release branch is 1.21. https://github.com/microsoft/terminal/releases Searching through the Changelog I don't believe the sixel changes landed in the 1.21 branch. |
It seems that Sixel support in the Windows Terminal is being worked on, and a PR for Sixel support in conhost has been merged (PR microsoft/terminal#17421).
The text was updated successfully, but these errors were encountered: