Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"Workspace symbols provider not found for current document"
See original GitHub issueIssue Description
I tried using :CocList symbols to jump to a symbol in the project but I keep getting this error for csharp projects. With rust it works. So I assume this is a coc-omnisharp issue.
Is this feature implemented? If so, how do we access it?
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (2 by maintainers)
Top Results From Across the Web
CocList symbols fails to find workspace symbols provider #1621
:CocList symbols fails with error [coc.nvim] Error on "CocList symbols": Workspace symbols provider not found for current document.
Read more >Scoping "Go to Symbol in Workspace" in VSCode to the entire ...
We previously only searched the project of the currently active file. This is controlled by the new "typescript.workspaceSymbols.scope" setting.
Read more >c_cpp_properties.json reference - Visual Studio Code
It tracks the current version of the c_cpp_properties.json file so that the extension knows what properties and settings should be present and how...
Read more >Lsp - Neovim docs
If no results are returned from any LSP servers, falls back to using built-in tags. Parameters: {pattern} (string) Pattern used to find a...
Read more >Troubleshoot WorkSpaces issues - AWS Documentation
My microphone or webcam is not working on Windows WorkSpaces. My users cannot login using certificate-based authentication and are prompted for the password ......
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
A related issue is that workspaceSymbolsProvider was not actually implemented by omnisharp-roslyn at all. This PR adds support for it:
+1