You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a .log file
Type the relative path and absolute path of a file in the workspace
The absolute path will be highlighted and clickable, but not the relative path
The text was updated successfully, but these errors were encountered:
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.
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.
🙁 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.
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
Steps to Reproduce:
.log
fileThe text was updated successfully, but these errors were encountered: