-
Notifications
You must be signed in to change notification settings - Fork 814
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
"ParseError: end of file reached" when using Textual in a pipe #3831
Comments
You may find this discussion helpful: #3818 |
Ah, that's what's going on. Thanks. |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
This work around was broken in 9a9b002, where the internal implementation switched from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When piping to a textual app, I get a
ParseError: end of file reached
error. There is also some random text at the beginning of the error msg (^[[?2026;4$y
) and there is also some left on the command line after (2026;4$yec^C
).Everything works correctly if I don't pipe to the app.
Using this code will cause the error:
Calling that file using any of these commands will cause the error:
This also happens if I pipe to a demo app.
Textual Diagnostics
Versions
Python
Operating System
Terminal
Rich Console options
Here is a screenshot and copy/paste of the output:
The text was updated successfully, but these errors were encountered: