-
Notifications
You must be signed in to change notification settings - Fork 815
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
Broken output on old windows cmd #3378
Comments
The reason for this is you're reporting this issue in the Textual repository. [Edit to add] The |
I found lots of references to |
I report it here because rich is working as expected but textual is not even though the rendering should be based on rich.
Thanks. I didn't find this before.
I tried setting it to |
I'm afraid Textual is unlikely to work in Windows 7. Microsoft introduce better terminal support in Windows 10. Prior to that it was abysmal. It would be possible to get it kind of working, but with disturbing visual glitches and it would be too slow to be useable. One option (other than upgrading) would be to use textual-web which runs a terminal in the browser. |
@willmcgugan What features did not work in Windows 7? I know that ANSI sequence support was added in Windows 10. But can they do anything which wasn't supported before by the Windows API? I thought that's exactly the thing colorama solved in the past before rich stopped using it. Or maybe I should ask: What terminal support is required for textual to work, but not required for rich? Since rich seems to work perfectly on Windows 7. Sorry, I don't want to sound impatient in the paragraph above. But sometimes I am annoyed by developers treating Windows as second class for development simply because the API is a different one compared to Linux/POSIX. Async development is similar, Windows had superior support for async for a long time compared to Linux (see I/O completion ports), just most developers didn't bother to learn it and tried to make the POSIX style work on Windows (which of course didn't work well). Please ignore the rant paragraph. |
Sorry for the slow response. The approach colorama and Rich takes for older Windows versions just wouldn't work for Textual apps. You only get 16 ugly colors and there is no explicit full screen support. You can't turn the cursor off. Even if you can tolerate those issues, the legacy terminal is incredibly slow. Until a few years ago Microsoft didn't consider the terminal to be a priority... |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
Windows 7 x64, cmd.exe
Python 3.8.10 x64
textual==0.38.1
rich==13.5.3
Colors are working fine with rich, however textual output is full of ANSI(?) sequences.
It is working on a Windows 10 machine with otherwise same environment. I remember in the past it worked on Windows 7 as well (maybe when colorama was still used?)
The issue template mentions a
textual diagnose
command which I cannot find anywhere...EDIT: maybe you meant
py -m rich.diagnose
?EDIT: after installing
textual-dev
Textual Diagnostics
Versions
Python
Operating System
Terminal
Rich Console options
The text was updated successfully, but these errors were encountered: