Skip to content

Enables sixel support for windows by using node-pty 1.1.0's copy of ConPTY instead of Window's older ConPTY - #8210

Open
blindmikey wants to merge 1 commit into
vercel:canaryfrom
blindmikey:canary
Open

Enables sixel support for windows by using node-pty 1.1.0's copy of ConPTY instead of Window's older ConPTY#8210
blindmikey wants to merge 1 commit into
vercel:canaryfrom
blindmikey:canary

Conversation

@blindmikey

Copy link
Copy Markdown

Fixes #8209

Bumps node-pty 1.0.0 -> 1.1.0 and passes useConptyDll: true, loading the ConPTY that ships with node-pty (1.23.251008001) instead of the one built into Windows. Older inbox ConPTY versions answer DA1 themselves without the Sixel attribute and filter DCS out of the output stream, so imageSupport never receives any image data on those builds.

Also run node-pty's post-install.js after rebuild-node-pty: node-gyp clears build/, and pnpm 10 does not run node-pty's own lifecycle scripts (onlyBuiltDependencies), so conpty.dll goes missing next to conpty.node and loading it fails at runtime.

Adds a useConptyDll config option (default true) to opt back out.

before: ESC[?61;6;7;21;22;23;24;28;32;42c (conhost answering, no 4)
after: ESC[?62;4;9;22c (xterm-addon-image answering)

This should be good to merge after review. Thanks for building such an awesome terminal! Happy to contribute in a small way.

…minal

Bump node-pty 1.0.0 -> 1.1.0 and pass `useConptyDll: true`, loading the
ConPTY that ships with node-pty (1.23.251008001) instead of the one built
into Windows. Older inbox ConPTY versions answer DA1 themselves without
the Sixel attribute and filter DCS out of the output stream, so
`imageSupport` never receives any image data on those builds.

Also run node-pty's post-install.js after rebuild-node-pty: node-gyp
clears build/, and pnpm 10 does not run node-pty's own lifecycle scripts
(onlyBuiltDependencies), so conpty.dll goes missing next to conpty.node
and loading it fails at runtime.

Adds a `useConptyDll` config option (default true) to opt back out.

before: ESC[?61;6;7;21;22;23;24;28;32;42c   (conhost answering, no 4)
after:  ESC[?62;4;9;22c                     (xterm-addon-image answering)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4.0.0-canary.5: Sixel support gets eaten by Windows ConPTY Fallback

1 participant