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

Relative file link detection in log files #238812

Closed
Metalit opened this issue Jan 27, 2025 · 3 comments
Closed

Relative file link detection in log files #238812

Metalit opened this issue Jan 27, 2025 · 3 comments
Labels
feature-request Request for new features or functionality output Output channel system issues

Comments

@Metalit
Copy link

Metalit commented Jan 27, 2025

When viewing .log files in the editor, absolute file paths will be detected as links, but not relative paths (to either the workspace root or the opened file). Notably this is different in the terminal, where relative paths are clickable without issue, and it would be useful if the detection in .log files was similarly flexible.

I am aware that you can insert file:// at the start and it will be detected in a link, but no log file is going to have this by default, and it doesn't work with line/column numbers regardless.

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.96.4
  • OS Version: Windows 11 10.0.22621

Steps to Reproduce:

  1. Create a .log file
  2. Type the relative path and absolute path of a file in the workspace
  3. The absolute path will be highlighted and clickable, but not the relative path
@sandy081 sandy081 assigned bpasero and unassigned sandy081 Jan 28, 2025
@bpasero bpasero added feature-request Request for new features or functionality output Output channel system issues labels Jan 28, 2025
@bpasero bpasero removed their assignment Jan 28, 2025
@vs-code-engineering vs-code-engineering bot added this to the Backlog Candidates milestone Jan 28, 2025
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality output Output channel system issues
Projects
None yet
Development

No branches or pull requests

4 participants