Skip to content
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

Strange empty spaces on the WSL terminal #328

Open
Kasui92 opened this issue Sep 13, 2021 · 7 comments
Open

Strange empty spaces on the WSL terminal #328

Kasui92 opened this issue Sep 13, 2021 · 7 comments
Labels

Comments

@Kasui92
Copy link

Kasui92 commented Sep 13, 2021

Describe the bug
When I open Windows Terminal on WSL2 where I installed powerline-go, there are gaps between the various components of the powerline (see photo below).

immagine

The error appeared to me after the recent update of Windows Terminal to the version 1.10.2383.0

To Reproduce
I don't know how to reproduce the error.

Expected behavior
It should appear as usual.

Environment (please complete the following information):

  • OS: Windows10
  • Architecture:
  • Shell: wsl bash
@jamieburchell
Copy link

Interestingly if you press enter or enter "clear" it seems to resolve itself too

@Kasui92
Copy link
Author

Kasui92 commented Sep 14, 2021

@jamieburchell
Confirm.

However, when I close and reopen the terminal for any other reason or simply open a new tab, the anomaly returns.

@justjanne
Copy link
Owner

Interestingly if you press enter or enter "clear" it seems to resolve itself too

That sounds like Windows Terminal knows how to render it correctly, it just doesn’t always do it. Seems tbh more like a Windows Terminal issue

@dswij
Copy link
Contributor

dswij commented Sep 16, 2021

Interestingly if you press enter or enter "clear" it seems to resolve itself too

That sounds like Windows Terminal knows how to render it correctly, it just doesn’t always do it. Seems tbh more like a Windows Terminal issue

+1, sounds like a Windows Terminal issue on the first draw. I don't have a Windows machine right now, but does this happens only on WinTerm + WSL or also on WinTerm + Psh? and does this happen to other prompts as well?

@Kasui92
Copy link
Author

Kasui92 commented Sep 16, 2021

Interestingly if you press enter or enter "clear" it seems to resolve itself too

That sounds like Windows Terminal knows how to render it correctly, it just doesn’t always do it. Seems tbh more like a Windows Terminal issue

+1, sounds like a Windows Terminal issue on the first draw. I don't have a Windows machine right now, but does this happens only on WinTerm + WSL or also on WinTerm + Psh? and does this happen to other prompts as well?

@dswij
I find this error only on the WSL terminal, not on pws and not even on the prompt.

@jamieburchell
Copy link

jamieburchell commented Nov 4, 2021

I don't have a fix, but as this annoys me every time I open the terminal, I've put clear at the top of my ~/.bashrc file to work around it.

@JanDeDobbeleer
Copy link

@justjanne this is a Windows Terminal bug -> microsoft/terminal#8341

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants