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

[Feature] Auto-detecting file URLs and make them clickable #9669

Closed
skyline75489 opened this issue Mar 30, 2021 · 3 comments
Closed

[Feature] Auto-detecting file URLs and make them clickable #9669

skyline75489 opened this issue Mar 30, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@skyline75489
Copy link
Collaborator

Inspired by #8166 (comment), we can also make the result of ls clickable if the CWD is provided. This is also possible in iTerm2. I'm not sure which sequence or technology it uses to detect the CWD, though. Anyway, with OSC9;9 recently added, this is also possible in WT.

Originally posted by @skyline75489 in #7526 (comment)

@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 Mar 30, 2021
@skyline75489
Copy link
Collaborator Author

I think this is what I prefer over #9661. And there is precedent like iTerm2 who handles the file URL detection very well.

@zadjii-msft
Copy link
Member

zadjii-msft commented Apr 2, 2021

You know, this sounds just like /dup #2671, so I'm just gonna move these comments there. Thanks though!

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Apr 2, 2021
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Apr 2, 2021
@ghost
Copy link

ghost commented Apr 2, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants