Tyler James Leonhardt
Tyler James Leonhardt
This would need to be supported in Core. Transferring there.
@yiliang114 I don't think this will be an easy one... but I'm open to discussing how we can achieve this.
@chriskuech > The vscode-powershell extensions cannot currently autocomplete user-defined functions/types that aren't in the same file. Autocomplete in PowerShell is based on what's available in a session. We use the...
I really really really really wish that this issue was an easy one to fix, but `$env:PSModulePath` is such a messed up environment variable that I think this issue is...
> (the ISE integrated terminal with intelisense) @gyro2death have you tried the [PowerShell Preview](https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell-Preview) extension with PSReadLine support in the integrated console?
VSCode has now added "quick fix all" 🎉 It should be in the latest insider build. We should see what work is involved on our side to enable this.
Here's what is required: "Each extension/language can implement quick fix all using the existing CodeActionProvider API" @Omniusz there are some perf related issues that are at the top of my...
ah I see... that's because the Terminal pane is open and by default it opens your default shell...
Yeah but... I don't know if we want to mess with other terminals... could be dangerous. The user might have been already running something in that other terminal.
Yeah. The extension would need an exclusion list. Feel free to open an issue in https://github.com/PowerShell/vscode-powershell