microsoft / microsoft/vscode-cmake-tools
Not all paths become a hyperlink in Output console on Windows
Open
Nobody has claimed this yet.
enhancement
Feature: other
help wanted
stale-exempt
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
Brief Issue Summary
Some of the tools I've integrated with CMake seem to output paths a bit weird (on Windows), which results in not all file paths being hyperlinked.
Expected:
Both example paths to be converted to a hyperlink:
D:\gitrepo\myfile.c:123:5D:/gitrepo\myfile.c:123:5
Apparent Behavior:
D:\gitrepo\myfile.c:123:5is converted to a hyperlink.D:/gitrepo\myfile.c:123:5is NOT converted to a hyperlink.
The difference is in the first slash (backward works, forward does not).
Platform and Versions
- Operating System: Windows 10 Pro 20H2
- CMake Version: 3.20.1
- VSCode Version: 1.56.2
- CMake Tools Extension Version: 1.7.3
- Compiler/Toolchain: Output is from PC-Lint Plus (so not a compiler but format is configured similar to GCC)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the VS Code Output console using the two Windows paths shown in the report. Locate the CMake Tools output path-hyperlink parsing entry point, then verify that both slash forms become hyperlinks and that existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100