Powershell does not open in current directory if its name contains a left square bracket (wildcard) #5752
Comments
@mklement0 Could you please comment the Issue? |
@iSazonov: The problem sounds closely related to #4726, as @enchanted13 has already pointed out. |
Hello. Author of the mentioned page here. Recently I ran into another issue, so I made a follow-up post. Until this issue is fixed, the only reliable way to open PowerShell in any folder would be some proxy application, doing all the required escaping, I think. |
@KillyMXI Hey, great follow-up post, I think this shows that native workarounds aren't really reliable for all the possible edge cases. A third party solution would be possible, but I really hope we can see these issues being fixed in powershell itself in the near future! |
Reverting the previous change due to side effects. Will have to revisit this later. |
just posted PR #7240 for this |
Steps to reproduce
Expected behavior
Actual behavior
Environment data
Additional Information
Hope this isn't a known issue, I've experienced it myself both when starting powershell from cmd and from Visual Studio Code ("Open in Terminal"). I've seen it discussed a little bit here. It might be related to Issue #4726. Hope we can see this fixed.
The text was updated successfully, but these errors were encountered: