Skip to content
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

Merge OSC1337-instance with SIXEL-instance #2

Open
junjihashimoto opened this issue May 22, 2020 · 2 comments
Open

Merge OSC1337-instance with SIXEL-instance #2

junjihashimoto opened this issue May 22, 2020 · 2 comments

Comments

@junjihashimoto
Copy link
Owner

junjihashimoto commented May 22, 2020

To support hterm of chromeos and iterm2, I've added OSC1337.
But ToOSC-typesclass is separate from ToSixel, so the usability is low.

@junjihashimoto
Copy link
Owner Author

junjihashimoto commented May 26, 2020

I am thinking using environment variables to detect terminal condition.
TERM variable of crostini is xterm-256color, though it does not support sixel.
So we have to define custom environment variable to choose OSC1337 or SIXEL.
How about using TERM_GRAPHICS variable?

@AutumnMeowMeow
Copy link

Unfortunately iTerm2 never made a clear means of identifying its image feature as a separate thing, unlike sixel support which is reported in device attributes. These days the XTVERSION sequence (see xterm ctlseqs) is used to detect terminals with iTerm2 (which AFAIK are hterm, iTerm2, mintty, and wezterm).

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

No branches or pull requests

2 participants