Repository navigation
Spaces added to prompt on shell launch (PowerShell/pwsh) #8341
Description
Environment
Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0
Windows Terminal Version: 1.4.3141.0
https://github.com/justjanne/powerline-go
Steps to reproduce
Add the following to your PowerShell $PROFILE (adjust the path to the powerline-go exectuable to your local environment)
Function global:prompt {
$pwd = $ExecutionContext.SessionState.Path.CurrentLocation
$startInfo = New-Object System.Diagnostics.ProcessStartInfo
$startInfo.FileName = "$ENV:OneDriveConsumer\Util\powerline-go.exe"
$startInfo.Arguments = "-shell bare"
$startInfo.Environment["TERM"] = "xterm-256color"
$startInfo.CreateNoWindow = $true
$startInfo.StandardOutputEncoding = [System.Text.Encoding]::UTF8
$startInfo.RedirectStandardOutput = $true
$startInfo.UseShellExecute = $false
$startInfo.WorkingDirectory = $pwd
$process = New-Object System.Diagnostics.Process
$process.StartInfo = $startInfo
$process.Start() | Out-Null
$standardOut = $process.StandardOutput.ReadToEnd()
$process.WaitForExit()
$standardOut
}Start a PowerShell (classic) or PowerShell terminal window via Windows Terminal. The first time the prompt function is called there are spaces inserted between the different prompt parts. Pressing Enter makes these disappear and the prompt works fine.
If I use the same profile without Windows Terminal launching PowerShell.exe directly it works fine. So I suspect this is related to Windows Terminal.
Here's an animated GIF that shows what is going on:
Expected behavior
I expect to see the prompt formatted correctly as follows:
Actual behavior
This is what the prompt looks like when the PowerShell is first started:
Reacted by Anson Heung, Wildan F. Abdillah, Philip Lonsing, Andrew S., Andreas Hopfgartner, Cyrus Yip, Arad Alvand, Purpzie and Nightliss
Activity
zadjii-msft commentedon Nov 20, 2020
This might sound crazy, but if you highlight that first prompt line, the one with the spaces, then dismiss the selection, does it re-render correctly?
DHowett commentedon Nov 20, 2020
It looks like you've customized your powershell profile somewhat? I can't reproduce this, but I am not using
-NoLogoor have otherwise suppressed the startup banner. 🤔DHowett commentedon Nov 20, 2020
Yeah, this only happens with
-NoLogo. Interesting!Mike Griese (@zadjii-msft) this is coming out of conpty with additional
\e[1Cin it, but only on the first-ever print to the screen. Everything else comes out fine.First run
After Clear
zadjii-msft commentedon Nov 20, 2020
well that's batty. Thanks for investigating! Dustin L. Howett (@DHowett) any chance you've got a oneliner repro for me that I can turn into a test? (if not that's cool too, this is probably enough to work off of)
EDIT: J/K read the OP again, that's simple enough. I was worried I had to install a module or something.
32 remaining items
Fix conpty not emitting colored spaces on the VERY FIRST frame (#13665)
Fix conpty not emitting colored spaces on the VERY FIRST frame (#13665)
Fix conpty not emitting colored spaces on the VERY FIRST frame (micro…
Un1q32 commentedon Dec 1, 2022
i seem to have a similar issue
It's different on different font sizes. The above screenshot is with a font size of 12, but with a font size of 13 the gaps disappear.
zadjii-msft commentedon Dec 5, 2022
@OldWorldOrdr Nah, that's more like, well, one of these: https://github.com/microsoft/terminal/issues?q=is%3Aissue+is%3Aopen+line+drawing
There's a few of those, so it's hard to point the finger at just one.