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
Double prompt when closing powershell extension terminal #4145
FWIW I'm also considering turning showOnStartupfalse by default, so that the terminal pane isn't opened when the extension activates, and then setting this to CloseAction.Restart automatically, which especially with the startInBackground option for those that never want to see the terminal could make the extension far less noisy, but also always on and working. Patrick Meinecke (@SeeminglyScience) thoughts?
for those that never want to see the terminal could make the extension far less noisy, but also always on and working
This is why I commented on #2418
I'd rather have a background instance remaining if I close it. Or alternatively, if I close the extension terminal in the GUI, that it doesn't actually delete it but just hides it the same way start in background does initially. Such that I can start it in background AND move it back to the background by closing it without having to close VS Code.
Fixed by #5380 (follow-up #5463). The double prompt came from the LSP client library showing its own "connection closed" notification on top of the extension's restart prompt. #5380 marks the client library's close action as handled, suppressing that duplicate, so only a single prompt is shown now. Closing as fixed — please reopen if you still see two prompts on a recent preview build.
Activity
andyleejordan commentedon Aug 19, 2022
Known issue, I've already filed a request upstream for us to improve this together: microsoft/vscode-languageserver-node#1057
andyleejordan commentedon Aug 26, 2022
FWIW I'm also considering turning
showOnStartupfalse by default, so that the terminal pane isn't opened when the extension activates, and then setting this toCloseAction.Restartautomatically, which especially with thestartInBackgroundoption for those that never want to see the terminal could make the extension far less noisy, but also always on and working. Patrick Meinecke (@SeeminglyScience) thoughts?Wallby commentedon Apr 7, 2026
This is why I commented on #2418
I'd rather have a background instance remaining if I close it. Or alternatively, if I close the extension terminal in the GUI, that it doesn't actually delete it but just hides it the same way start in background does initially. Such that I can start it in background AND move it back to the background by closing it without having to close VS Code.
andyleejordan commentedon Jun 16, 2026
Fixed by #5380 (follow-up #5463). The double prompt came from the LSP client library showing its own "connection closed" notification on top of the extension's restart prompt. #5380 marks the client library's close action as
handled, suppressing that duplicate, so only a single prompt is shown now. Closing as fixed — please reopen if you still see two prompts on a recent preview build.🤖 Drafted by Copilot for Andy Jordan (@andyleejordan) to review/edit.