Change:
const windowsFallbackLinks: (string | { link: string; resource: URI })[] = [ 'C:foo bar', 'C:foo barbaz', <del> 'C:foobar baz' </del> <ins> 'C:foobar baz', 'C:foo/bar baz' </ins> ]; const supportedFallbackLinkFormats: LinkFormatInfo[] = [ // Python style error: File "<path>", line <line> { urlFormat: 'File "{0}"', linkCellStartOffset: 5 }, { urlFormat: 'File "{0}", line {1}', line: '5', linkCellStartOffset: 5 }, <del> // A C++ compile error </del> <ins> // Some C++ compile error formats { urlFormat: '{0}({1}) :', line: '5', linkCellEndOffset: -2 }, </ins> { urlFormat: '{0}({1},{2}) :', line: '5', column: '3', linkCellEndOffset: -2 }, <ins> { urlFormat: '{0}({1}, {2}) :', line: '5', column: '3', linkCellEndOffset: -2 }, { urlFormat: '{0}({1}):', line: '5', linkCellEndOffset: -1 }, { urlFormat: '{0}({1},{2}):', line: '5', column: '3', linkCellEndOffset: -1 }, { urlFormat: '{0}({1}, {2}):', line: '5', column: '3', linkCellEndOffset: -1 }, { urlFormat: '{0}:{1} :', line: '5', linkCellEndOffset: -2 }, { urlFormat: '{0}:{1}:{2} :', line: '5', column: '3', linkCellEndOffset: -2 }, { urlFormat: '{0}:{1}:', line: '5', linkCellEndOffset: -1 }, { urlFormat: '{0}:{1}:{2}:', line: '5', column: '3', linkCellEndOffset: -1 }, </ins> // The whole line is the path { urlFormat: '{0}' }, ];

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --Version: 1.76.2 (user setup) Commit: Date: 2023-03-14T17:55:54.936Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0. Sandboxed: No Problem: There are some situations where the a path cannot be completely be detected as a link when spaces are contained in the path. This can be easily be reproduced when a compilation error/warning is reported from a file in Program Files (Windows). Here are some example of file paths not being detected properly with different compilers. Visual Studio (CL) ! Clang: ! nvcc (NVIDIA CUDA compiler) ! Surprisingly, this use case works (nvcc): ! Steps to Reproduce: a C++ file in a folder that contains a space that file in the terminal (I am launching the compiler as a task)
I believe this is already fixed, can you see if you can reproduce in the ? /label info-needed
The link improvements that cover this were in 1.75: This is why the 4th case is working.

Will look into it
I'm surprised to see the 4th case working considering the regex requires a space before the
I see the column is required above which is wrong
I am reproducing the same behavior with the Insider build : Version: 1.77.0-insider (user setup) Commit: Date: 2023-03-29T09:56:00.839Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes
Thank you for your quick response!