Closed pitgrap closed 2 years ago
@pitgrap that’s a known Windows Terminal bug. You can find more information and a fix here. Although the "startup" issue is related it only manifests once. Adding clear
at the end of your profile also resolves it.
@pitgrap that’s a known Windows Terminal bug. You can find more information and a fix here.
I tried it, but it doesn't work. (Or I put the the codeblock on a wrong place in the theme json?).
Although the "startup" issue is related it only manifests once. Adding clear at the end of your profile also resolves it.
Haha, sometimes workarounds are so simple. 'DOH. Thank you so much for your fast feedback! Love it.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
I'm using oh-my-posh with WSL2 (Ubuntu) in a latest Windows Terminal (Win10). Installed via brew. Nerdfonts (Caskaydia Cove) is installed. Everything works fine, but on startup there are empty spaces in the prompt. After hitting enter, or doing anything in the terminal it looks good again. This is not a big deal, but somehow it disturbes me. ;)
A separate oh-my-posh in the powershell does not have this problem.
Theme
pradadox, but happens with every theme.
What OS are you seeing the problem on?
Windows, Linux
Which shell are you using?
bash
Log output