Add experimental support for icy_sixel #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds experimental support for icy_sixel as an alternative for libsixel, guarded by the
icy_sixel
feature flag.Why
icy_sixel
?sixel-sys
has issues to build in Windows and seems to be a bit tricky to fix (Windows Terminal Preview supports Sixel).Other notes:
icy_sixel
and I haven't tested it a ton. So the feature flag should definitely be marked as experimental. It seems to run fine though :-).sixel_util
module, that is compiled, if eithersixel
oricy_sixel
is enabled.check_sixel_support()
, to check for theWT_SESSION
environment variable, which is set by Windows Terminal (may not be the best way of detecting it, but seemed to be the simplest change). The code will then just assumetrue
, because runningcheck_device_attrs()
was giving me trouble. As a precaution, the if-branch is only compiled in, ificy_sixel
is enabled.sixel
andicy_sixel
are enabled, the code will useicy_sixel
. This seemed reasonable, as it is the more specific feature flag.Extending
viu
to also support theicy_sixel
feature flag would be appreciated (should be a trivial pass-through).