Enable sixel support in VTE if it's available. #770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Can you remove the flake.nix file? We don't keep os-specific build files in the repo. Other than that, thank you very much! |
Tyler-Hardin
force-pushed
the
master
branch
2 times, most recently
from
d70a0e0
to
0fea7d4
Compare
|
Oops, accidentally closed while trying to remove the flake commit. |
|
Thanks for the PR! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The actual sixel related change is very small. It should be safe and (I hope) uncontroversial.
The flake.nix I used to dev/test this is also included. It enables one to (relatively) easily install a modified instance of VTE compiled with SIXEL support included. If it's unwanted, I don't mind dropping it from the pull request. I'm sorta new to Nix so I doubt it's perfect.