-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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 forward slashes in autocomplete on Windows #15764
Comments
This is by design. The directory separator on Windows and linux are different. Making this configurable would require us to also make changes to the native command processor because many win32 executables require backslashes. |
As far as I remember, I don't use any application that requires backslashes. Everything I work with expects forward slashes (they might accept backslashes for backward compatibility). Given the problems that Powershell already has for calling native applications (#1995 and #13068), I don't think that conflicts with this issue. |
This issue has been marked as by-design and has not had any activity for 1 day. It has been closed for housekeeping purposes. |
Both |
The strange behaviour is that it doesn't keep what I have already written! So I have to avoid autocomplete altogether. |
@aminya Good point, it'd be nice at least if I started typing |
Summary of the new feature / enhancement
I have been trying to avoid using
\
for path separation, but PowerShell still uses\
in its autocomplete when I press TAB. Could you make this configurable so it uses/
instead?Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: