Maybe a third option?

There's definitely some folks who never want to see it and often spam close terminals instead of hiding the pane. No idea how many, maybe it'll just be a vocal few. But I think changing the way this setting currently works will result in another surge or false positive "it doesn't work sometimes" issues.

Mostly just wanted to voice that concern, I'm cool with trying it out in a preview if you still want to.

Future work: we're going to flight switching the default of showOnStartup, and add to the upcoming PowerShell Walkthrough a step which shows how to re-enable it.

We want folks to use the PSIC though. If they don't, F8 stops working properly, intellisense doesn't reflect the context of the terminal they're in, when they start debugging they will all of a sudden be in a different context.

That default makes sense if you're only occasionally using PowerShell but if it's your primary workload that's going to be detrimental.

@SeeminglyScience I'll chat with you virtually, I think there's some crossed wires here.

Sounds like maybe we'll add a "Background Process" option.

Sounds good, let's trial it.

We want folks to use the PSIC though. If they don't, F8 stops working properly, intellisense doesn't reflect the context of the terminal they're in, when they start debugging they will all of a sudden be in a different context.

I know this is a bit dated but I'm confused on this area as I intentionally use Code terminal over integrated just for stability and "it runs the same on my machine". Since it more closely mimics running scripts outside of VS Code. I also had issues with integrated using dbatools module and developing in large workspaces like dbatools.

Either way, F8 and Intellisense worked fine for me using Code terminal when I have that setting set to false. I import a module into the terminal and had full Intellisense of that module with no issues.

I know this is a bit dated but I'm confused on this area as I intentionally use Code terminal over integrated just for stability and "it runs the same on my machine". Since it more closely mimics running scripts outside of VS Code. I also had issues with integrated using dbatools module and developing in large workspaces like dbatools.

A large focus of the extension is to keep the console working the same as an external one. Have you reported the issues you encountered?

Either way, F8 and Intellisense worked fine for me using Code terminal when I have that setting set to false. I import a module into the terminal and had full Intellisense of that module with no issues.

If the module is in your PSModulePath then intellisense will work, but it's not related to the code you executed with F8. We get intellisense only from the Extension terminal, any others will have no effect on intellisense (aside from things like installing a module ofc).

A large focus of the extension is to keep the console working the same as an external one. Have you reported the issues you encountered?

Most of it was known issues way back when, when you loaded modules that had a high number of DLL libraries. This was well before all the rewrite that Andy started working on. If I come across it on latest release I will be sure to submit issues.