[BUG] table line missing characters in windows terminal but not cmd
See original GitHub issueDescribe the bug
Running python -m rich
in the latest windows terminal outputs three ??? characters in the line under the column headings.
To Reproduce
Platform
- Windows 10
- Windows terminal 1.1.2021.0
- Python 3.8.2
- Rich 4.2.0
- Happens with Cascadia, Cascadia Mono, Consolas. Assuming all fonts
- Doesn’t happen in cmd/powershell/conemu
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
[BUG] table line missing characters in windows terminal but ...
Describe the bug. Running python -m rich in the latest windows terminal outputs three ??? characters in the line under the column headings....
Read more >Windows Terminal Troubleshooting | Microsoft Learn
Learn fixes to common obstacles in Windows Terminal. ... Ctrl+= does not increase the font size; The text is blurry; My colors look...
Read more >How to use unicode characters in Windows command line?
The most secure solution is this one: Go to your Registry key HKEY_CURRENT_USER\Software\Microsoft\Command Processor and add String value ...
Read more >Python on Windows FAQ — Python 3.11.1 documentation
If so, the window will disappear after you call the exit() function or enter the Ctrl - Z character; Windows is running a...
Read more >Bash Reference Manual - GNU.org
A Unix shell is both a command interpreter and a programming language. ... A non-quoted backslash ' \ ' is the Bash escape...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in v4.2.1
Tested on the original PC and it still happens, but tested on another Windows 10 one and it doesn’t, so I’m chalking it up to an environment issue on this PC. Thanks for your work on this.