-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
"Windows PowerShell" message line wrapped when opening integrated terminal #6733
Comments
Note that this is less important now with cmd.exe becoming the default (#6886). This is what the HTML shows:
|
The follow data is received from Powershell:
This is the one that adds all the spaces:
|
Stepped through the code, the second message is
|
We could intercept this message and fix this case, but the greater question is why Powershell would tell us to go to the 64th column. Powershell correctly passes |
Compare this to the first message from cmd:
|
@lzybkr sorry to bother you again, but have you got any ideas on this? Powershell seems to be telling our terminal to go to the 64th character for some unknown reason. |
PowerShell doesn't generate any VT100, and I don't see any code that sets the cursor position before displaying the logo - so I'm at a loss how that could happen. The banner message doesn't even start out with any whitespace or newlines. |
Maybe it's pty.js doing this then, I'll have a look there thanks. |
Looks like this is where it happens, still looking into why: https://github.com/platformio/pty.js/blob/prebuilt/deps/winpty/agent/Terminal.cc#L372 |
From my digging yesterday it seems like some obscure at the depths of the old version of winpty being used. Moving to backlog for now due to lower priority as well as no time to fix for May. |
While I can't reproduce this anymore, I believe this was happening because the shell process did not have dimensions set on start up. To verify:
|
testing #6654:
When opening the integrated terminal I see this:
The message "Windows PowerShell" has a very large indent which makes it wrap at the edge of the view port. The native PowerShell console shows the message left aligned:
The text was updated successfully, but these errors were encountered: