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

Ctrl-click: support FS paths such as C:\ and C:/ #10429

Closed
mitranim opened this issue Jun 15, 2021 · 4 comments
Closed

Ctrl-click: support FS paths such as C:\ and C:/ #10429

mitranim opened this issue Jun 15, 2021 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@mitranim
Copy link

mitranim commented Jun 15, 2021

Description of the new feature/enhancement

As of 1.8.1521.0, Windows Terminal supports some file URLs:

file://C:/<path>
file:///C:/<path>

But support for regular FS paths seems to be lacking:

C:\<path>
C:/<path>

Being able to Ctrl-click into files and folders would be extremely convenient.

The reason I'm also asking for / support, in addition to \, is because certain CLI tools may output these partially "unixified" paths. For example, Go stacktraces have paths that look like this:

C:/<path>:<row>:<col>

(Support for row/col is a separate issue: #10428. This is about FS paths which may use both slash styles.)

@mitranim mitranim added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 15, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 15, 2021
@skyline75489
Copy link
Collaborator

I think #2671 covers this.

@mitranim
Copy link
Author

Should I add examples to that issue?

@skyline75489
Copy link
Collaborator

Feel free to do so if you want to. We know what the feature is about. Just lack a solution that handles all scenarios (cmd, powershell, WSL & possible other shells). See #9793 (comment) .

@mitranim
Copy link
Author

Closing as duplicate, apologies for your time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants