-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for \x1b escape characters #7
Comments
I would assume it could be done in a pretty easy way by simply just checking if either of those characters are in the data and then just add it to the data written. I might have to do a good overhaul of this library when I fix this, it surely would do it good to match PEP8. Some Python experience has been gained since I started this. Do you think this is sufficient? If not please provide some actual data where the characters are needed and included, then I can also make some testcases for this.
|
Thanks for the fast reply and sorry for the confusion, with ESC, I meant the escape character 27, sometimes refered to as I was thinking more along the lines of:
lmk |
Hello. Yeah you are right. Some additional characters are needed!
|
@gijsn Any updates on this? |
I have released a 0.1.1 and closing the issue. |
According to the manual, section 7, any USB control characters like '+' and 'ESC' that are used as data and not for control need to be additionally escaped by the escape character
\x1b
. Is there a way to logically implement the support for such escape sequences?Thanks
The text was updated successfully, but these errors were encountered: