notpeter
commented
3 days ago Hi @gdamore,
Thanks for pointing mentioning problem matchers, I was not previously familiar with them. It seems like it's basically a regex with capture groups for [file, line, column, severity, message, code] and then a mapping of numerical capture group numbers for each.
- https://code.visualstudio.com/docs/editor/tasks#_defining-a-problem-matcher
- https://github.com/actions/toolkit/blob/main/docs/problem-matchers.md#single-line-matchers
- https://github.com/microsoft/vscode/blob/2aeb8d55a0b473b1a5a6f0ff5faa3fa847d662a4/src/vs/workbench/contrib/tasks/common/problemMatcher.ts#L1491-L1602
Can you give an example of the output which you are looking to match from the D compiler?
We've recently incorporated some improvements detecting more styles of file:(line,column) references as clickable url in terminal:
But perhaps a more generalized approach is warranted, e.g. allowing language extensions and user settings to provide more niche matchers.
Check for existing issues
Describe the feature
The tasks feature is great in Zed, but it would be good if it could support problemMatcher like VSCode can. We need this for D, as our compiler emits error messages in a somewhat unconventional way.
It would be extremely nice to be able to clink on a link and go right to the source of the problem.
If applicable, add mockups / screenshots to help present your vision of the feature
No response