Alex Ross

@chrmarti for LocalForward.

This is a VS Code bug: https://github.com/microsoft/vscode/issues/152036. Should be fixed in the next VS Code recovery release (likely this week).

I'm not sure if the change in the PowerShell grammar is intentional. I've updated the first comment above to include some extra details for the owners of the grammar. If...

@stefanita-mitran I can reproduce this, but it also occurs in PowerShell ISE. I'll move this issue to the owners of the PowerShell grammar.

@msftrncs 👌. Thank you for detailing the correct behavior here. Sounds like this will be fixed with PR #156

Ah, I thought there was some extra change need to get to the correct behavior in https://github.com/PowerShell/EditorSyntax/issues/161#issuecomment-470231962. Thanks for confirming that it is already correct.

It looks like the terminal might be. @dauphine-dev could you install the latest Insiders build of VS Code and see if you're still seeing the issue?

~~The task system should really be resolving that before it hands over to the terminal. I'll try that repro.~~ Nope, it shouldn't we only find executable for windows. @Tyriar, is...

@Tyriar makes sense! Summary: The issue occurred when the `command` of a `process` task was also the name of a folder. It is fixed in VS Code Insiders for Windows...

There is no setting to disable this behavior. I'll take it as a feature request to add a setting for it.