Add: ByteScreen, use_c1 option #174
Open
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
|
Thanks @eight04!
Looking at the diff, you should be able to keep these modifications local to your project? |
|
Currently I package the modified version of pyte into my app: Do you know any pyte alternative that accepts bytes? |
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.
Fixes #118
This PR adds two features:
ByteScreen- a screen that accepts any char, including unprintable/zero-width chars e.g. (\xad).ByteStream(screen, use_c1=False)- allowing us to stop parsing CSI_C1/OSC_C1 bytes so they can be piped toByteScreen.