Justin Grote

> @JustinGrote, wouldn't it be possible to hook 2 consoles into the VSCode environment, one the user interacts with and one that is more or less "read only" per say...

It's still an experimental feature: https://code.visualstudio.com/docs/editor/integrated-terminal#_shell-integration So it's unlikely to be the *default*, however we could look into adding a feature flag for it. The PSIC is not a normal...

I noticed in the documentation they said they shim in a .ps1, so that wouldn't be that hard to just add a setting to call it if that's all it...

There are cases where you might want it for your integrated terminal but not PSIC, but yes, extensions can read settings and it would probably be gated behind both these...

FWIW you can hit ctrl-space to get the possible values, and then if your `editor.tabCompletion` setting is set to `on`, it will behave as you expect 

I'm going to re-flag this as a potential enhancement, as the behavior is as expected. As noted by @MartinGC94, completion would need to be enabled as a trigger for a...

Right, just throwing this up here as a nice to have to make sure it's documented at least.

@ztrhgf maybe you can provide some specific examples of where it fails? I'm on preview and intellisense works just fine for me. Screenshots are welcome!

Hard to say if example 1 is reasonable, it feels like the editor should be showing you an error that the type doesn't exist (yet), but that's a whole 'nuther...

We could try an experimental feature with a filewatcher that watches for .ps1 changes and automates this process, that might be better suited to a one-off extension since it probably...