You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pressing CTRL+C to cancel script doesn't stop debugging in preview extension #3700
I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
Summary
I just installed preview extension to see if Write-Host is fixed yet, and noticed it wasn't, so during a long time script running I press CTRL+C, but while the script stopped, GUI doesn't think so.
Also can you test if this repros with PowerShell 7.2? While I wired up a stop debugging notification so that stopping the PowerShell debugger informs Code to stop the GUI, I don't think it is supported with PowerShell 5.1
I refuse to use preview until this is fixed because it ruins the output of my programs. My modules heavily rely on Write-Host and it makes it really bad.
Activity
andyleejordan commentedon Nov 23, 2021
Przemysław Kłys (@PrzemyslawKlys) Can you link the tracking issue for "Write-Host is fixed yet, and noticed it wasn't"?
andyleejordan commentedon Nov 23, 2021
Also can you test if this repros with PowerShell 7.2? While I wired up a stop debugging notification so that stopping the PowerShell debugger informs Code to stop the GUI, I don't think it is supported with PowerShell 5.1
PrzemyslawKlys commentedon Nov 23, 2021
It's not only PowerShell 5.1
Notice how I stopped CTRL+C and was able to type stuff in a terminal, while the GUI was showing something different.
Write-Host -NoNewLinenot respected #3651I refuse to use preview until this is fixed because it ruins the output of my programs. My modules heavily rely on Write-Host and it makes it really bad.
andyleejordan commentedon Nov 23, 2021
Cool, thanks for the information.
andyleejordan commentedon Nov 23, 2021
It looks like the wiring up I did in PowerShell/PowerShellEditorServices#1570 was unfortunately not carried over in the pipeline threading rewrite PowerShell/PowerShellEditorServices#1459.