-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Bash for Windows terminals wrapping over 80 characters, terminals aren't sized correctly #106668
Comments
See this video for a demonstration of the bug: https://vimeo.com/452916914 |
This is nothing to do with remote-wsl or wsl in general, it happens when the extension is disabled as well. |
The fact that 0x0 is used initially followed by the actual dimensions right after is indeed the reason this doesn't work only for git bash under conpty. The reason 0x0 is used (which falls back to 80x30) is a little more complicated. Historically we have provided the terminal container in order to get the dimensions of the terminal when we can, which may or may not have happened depending on how the terminal was created. Basically we could only get the dimensions if the terminal panel had been shown before and it was not going to be a split. But this seems to have fallen apart I think after integrating the terminal with the new "view" system. Quick fix: Disallow |
To verifier:
|
I was able to reproduce this in the recent insiders using a single terminal: https://memes.peet.io/img/20-10-3d8a2c7c-818b-4921-9c84-d78cf33d217e.mp4 |
@connor4312 I repro'd the issue on stable, then tried in insiders and verified that it was fixed. Given that this is intended to be a quick fix, and that there's an intended thorough fix (#106672), I'm going to close this and call it verified, since it does solve the issue for me. |
1.48.2 (user setup)
Commit: a047975
Date: 2020-08-25T10:13:11.295Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: