Skip to content
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

Closed
aminya opened this issue Jul 13, 2021 · 6 comments
Closed

Use forward slashes in autocomplete on Windows #15764

aminya opened this issue Jul 13, 2021 · 6 comments
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-By Design The reported behavior is by design. WG-Interactive-IntelliSense tab completion

Comments

@aminya
Copy link

aminya commented Jul 13, 2021

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?

pwsh-path-autocomplete

Proposed technical implementation details (optional)

No response

@aminya aminya added Issue-Enhancement the issue is more of a feature request than a bug Needs-Triage The issue is new and needs to be triaged by a work group. labels Jul 13, 2021
@iSazonov iSazonov added Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a WG-Interactive-IntelliSense tab completion and removed Issue-Enhancement the issue is more of a feature request than a bug labels Jul 13, 2021
@theJasonHelmick
Copy link
Collaborator

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.

@theJasonHelmick theJasonHelmick added Resolution-By Design The reported behavior is by design. and removed Needs-Triage The issue is new and needs to be triaged by a work group. labels Jul 29, 2021
@aminya
Copy link
Author

aminya commented Jul 29, 2021

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.

@ghost
Copy link

ghost commented Jul 30, 2021

This issue has been marked as by-design and has not had any activity for 1 day. It has been closed for housekeeping purposes.

@ghost ghost closed this as completed Jul 30, 2021
@parkovski
Copy link

Both wsl and cmake require forward slashes so autocomplete doesn't work with them. Yes, some other tools require backslashes. Windows is a "both" system, not a backslash only system, and it'd be nice to have this acknowledged.

@aminya
Copy link
Author

aminya commented Aug 28, 2021

The strange behaviour is that it doesn't keep what I have already written! So I have to avoid autocomplete altogether.

@parkovski
Copy link

@aminya Good point, it'd be nice at least if I started typing ./ or SomeFolder/ if it would complete forward slashes.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-By Design The reported behavior is by design. WG-Interactive-IntelliSense tab completion
Projects
None yet
Development

No branches or pull requests

4 participants