Request - parse dmd exception output to make it compatible with vscode linkify
See original GitHub issueThe exception output format is e.g.
core.exception.AssertError@tests/optional.d(450): unittest failure
So vscode cannot recognize it as a file link since there’s no file called core.exception.AssertError@tests in the cwd.
I wonder if there’s anyway code-d can help out here?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Language Server Extension Guide - Visual Studio Code
Explain how to build a Language Server extension in VS Code using the provided Node SDK. Explain how to run, debug, log, and...
Read more >awesome-vscode | A curated list of delightful VS Code ...
A curated list of delightful Visual Studio Code packages and resources. For more awesomeness, check out awesome. Awesome Build Status. Table of Contents....
Read more >vs code Problems with C# extension, Some projects have ...
Please review the output for more details. I check the output and this is what I find. Starting OmniSharp server at 2/17/2021 ...
Read more >REST Client Extension for Visual Studio Code - GitHub
If request method is omitted, request will be treated as GET, so above requests are the same after parsing. Query Strings. You can...
Read more >Apex Interactive Debugger | Salesforce for VSCode
In VS Code, create a launch configuration for Apex Debugger. ... The Call Stack panel in the Debug view shows the name of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

there is now a proposed API in VSCode insiders so I am finally able to do this: https://code.visualstudio.com/updates/v1_47#_terminal-link-provider
It might still change and won’t be usable for normal users at least before 1.48 though.
uh well after looking into it, it was actually compiler errors which I parsed so this wouldn’t really be affected after all