This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Conversation
Author
|
at least one kernel (NyauxKC) uses this, so it's production ready :^) |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
just synced to trunk and made a few changes.
everything works the same way as the normal flanterm, but user can now print sixels by passing the full string to
term_writechanges to the user api:
_freepassed toflanterm_fb_initno longer includessize_t sizeargument.ctx->deinitno longer takes a_freeas an argument._mallocand_freeare NULL, sixel support is disabled.