Raoul Wols

What's the status on this now?

With version 1.5 of LSP, plugins can now define an on_open_uri_async callback. https://github.com/sublimelsp/LSP/blob/97e138e8e3300e52140569f3ada95e05d5b8d9bc/plugin/core/sessions.py#L603-L614 The LSP-jdtls helper package can override this method and define what to do with `jdt:` schemes. I...

@daveleroy does sublime_debugger expect anything special of a sublime View in particular to be able to attach to it or recognize it? the way this view with "virtual content" is...

> until/if LSP switches over to 3.8 We're blocked on dependencies: https://github.com/sublimelsp/LSP/issues/1389 https://github.com/wbond/package_control/issues/1518

I've enabled LSP-jdtls to understand `jdt:` URI schemes. But the actual opening of the URI should be done from the DAP side. See: https://github.com/sublimelsp/LSP-jdtls/pull/15#issuecomment-900191073

This is now moving to dumping data in `sublime.cache_path()/../Package Storage` (or some variation on that) due to ST scanning package folders for resources.

I've checked out this repository, but there are more problems on the horizon. Everywhere where pyls takes a `position` or a `range` in the request method, we should do the...

By the way, if all source code is ASCII (most common case), then the problem won't show itself.

Correction: if the source code contains characters from the basic multilingual plane, then UTF-16 can encode that in one code point, so those characters will work by accident too.

IMO this (getting `Exception($0)`) is the right thing to do because textDocument/signatureHelp will tell you what the arguments should be. In case the text editor doesn't have the signatureHelp capability,...