Allow to hide the PowerShell Integrated Console from the user

Summary of the new feature

As a user I want autocompletion etc., but without having the PowerShell Integrated Console in my Terminal view, so that when I open the Terminal view, I don’t accidentally start using it.

Say I have 5 files open in VS Code: if none of them is a PowerShell script and I hit Ctrl+` , VS Code gives me a standard powershell terminal that I can use straightaway. However, if I happen to have a PowerShell script open, I just get the already-running PowerShell Integrated Console (which I don’t want to use, because it doesn’t quite work the same like a standard terminal).

Proposed technical implementation details

If I understand this correctly, there’s a TerminalOptions.hideFromUser API to do exactly this.

So what I’d like to have, is an extension setting to specify that the PowerShell Integrated Console should be launched with hideFromUser set to true.

[TylerLeonhardt]

Gotcha. So I guess we can kinda support this by using hideFromUser at start up instead of “not running show” and then debugging should “unhide” the terminal.

Unfortunately, once it’s shown, we wouldn’t be able to re-hide it like you said… but this should be good for @anthonyvdotbe maybe?

[anthonyvdotbe]

Does this also cover your case?

It doesn’t: that setting only prevents the Terminal view from being shown as soon as a PowerShell script is opened, but the PowerShell Integrated Console is still there. So when I hit Ctrl + ` , I’ll end up in the PowerShell Integrated Console, rather than a standard powershell terminal.