Consider lsp subcommand to properly handle communication about distant HOT 5 CLOSED

Another advantage of this being done on this side is it opens up distant for lsp against other editors without needing to write lsp hacks on clients individually. All that would be needed is special handling of distant scheme.

from distant.

Instead of the explicit types, may just be easier to search through keys of json message.

Write some function that provides us the full json path to the current value in the form of "path.to.value" supporting array "path.to[1].value" and object "path.to[key].value", if this is useful.

At least, supports iterating through all keys nested, determining if starts with file: or distant:, and letting us swap.

from distant.

If we were to just do json field substitution without types, named fields that include DocumentUri or Uri types w/ spec 3.16 are:

• uri
• targetUri
• href
• oldUri
• newUri
• changes object of WorkspaceEdit whose keys are document uris
• scheme on DocumentFilter and FileOperationFilter is just the scheme part of the URI
• rootUri of InitializationParams (deprecated, but still a URI)
• scopeUri
• target

from distant.

Maybe resolved by 260cb0e as this adds an LSP command that parses requests and responses into JSON, replacing schemes as described above.

from distant.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from distant.