-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use backslash instead of forward slash #10
Comments
When you hit tab it autocompletes as |
Oh I see. The problem is PowerShell not cmd. Thanks for the bug report. |
@aklietz I was too quick to send a report though; here is the actual problem: both It does work in paths that don't require double quotes though, even with a final backslash |
@alesimula , this is a bug in PowerShell tab completion; see PowerShell/PowerShell#7400. The usual command line parsing code for windows CLI EXEs interprets a There's some background in the comment I made for a quoting issue within For now, it looks like the problem is "fixed" for PowerShell versions of v6.0+. Although I wouldn't bet on a complete/final solution yet... command line processing and handoff is still a big work-in-progress for them (see PowerShell/PowerShell#1995 (comment) and PowerShell/PowerShell#15143). The only way to "fix" this within $0.02 ref: David Deley ~ "How Command Line Parameters Are Parsed" @@ https://archive.is/LTgTs |
Windows uses backslashes for paths, but running such command
would not work as it expects a forward slash; this makes msls a bit frustrating to use with autocomplete, there should be an option to use backslashes as path separators
The text was updated successfully, but these errors were encountered: