My project has files like "Bar`1.cs" to represent generic types, as is done in the dotnet SDK.
My build task contains "problemMatcher": { "base": "$msCompile" }.
When such a file has errors/warnings, I get this:
/home/username/project/Foo/Bar`1.Tests.cs (458,23): warning 123: some warning [/home/username/project/Foo.Tests.csproj]
...which is fine. But I cannot control-click on that filename to open it. The file's path is not underlined as normal - there is a clickable part before the bactick, and after.
How can I fix the click behaviour without changing filenames (impossible)?
This bug seems to be been fixed.