try to get the Pkg.test subprocess to detect sixel compat #29
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.
Currently
is_sixel_supported()
returns false within Pkg.test within a terminal that otherwise returns true, which is a shame because that's one of the most useful places for Sixel to run.I think it's something to do with stdin not being forwarded properly by Pkg.test.
@oxinabox I recall you reported an issue like that in the past, but I couldn't find it in Pkg.jl issues.
Note stdin isn't forwarded here https://github.com/JuliaLang/Pkg.jl/blob/12c3eaf1a896edfc21bb935500bf905d42067a8a/src/Operations.jl#L2437
So in Sixel tests via Pkg.test we get