Raoul Wols

We now have an official client capability for this as well https://github.com/microsoft/language-server-protocol/commit/8aec48a51caf88e5c58cb082828abe028eb08396

I understand the problem, but the fix is non-trivial. Some language servers like clangd return high-quality fuzzy matches. These work remarkably well with ST's internal fuzzy prefix matching. And I...

In your example above, you expect to only see `Decode.map` as completion, right? Your text edit would look something like ``` { 'newText': 'Decode.map', 'range': { 'start': {'line': 26, 'character':...

Package Control WIP branch is at https://github.com/wbond/package_control/tree/four-point-oh

Maybe not a real solution, but can you instead try running the OmniSharp.exe file under mono? ``` "command": ["mono", "/Users/ryanjoseph/.vscode/extensions/ms-dotnettools.csharp-1.23.8/.omnisharp/1.37.5/path/to/OmniSharp.exe", "-lsp"] ``` Although, I don't know if a global `mono`...

The bug is that we don't kill child processes in all possible cases IMO. The fact that running omnisharp under mono works around this issue is... a workaround :)

I am surprised "next_result" actually works. Why does it work at all? All we do is call view.add_regions, right? Do these regions automatically count towards a view's "problems"?

I'll consider this an ST issue. The problem is that ST doesn't have a notion of diagnostics at all, or a notion of a problems panel like VSCode. Therefore ST...

I mean exactly the same problem occurs when you have a build system with a file or line regex, and the annotations appear in the view, and you edit the...

So we should remove diagnostics once the buffer is modified?