Rafał Chłodnicki

ST provides functionality to show annotations at the right-hand side of the view (not immediately after the text like in VSCode). It was tried in https://github.com/sublimelsp/LSP/pull/1214 but wasn't ideal.

Now that I look at it, that PR was only doing that for diagnostic intersecting with the cursor.

Implemented a proof on concept based on @rwols PR here: https://github.com/sublimelsp/LSP/pull/1702 Feel free to test it out (have to clone the repo manually).

The server sends two changes to fix formatting. The first that removes the whole 6th line and the second that adds back formatted one. Server response ``` [ { "newText":...

It's most likely handled at the core level of the editor. Maybe VSCode handles that case better. We are just using ST's APIs to remove and add regions as instructed...

I was thinking that we could process the payload ourselves to create a minimal change. We could do that by applying changes in memory and then creating minimal change from...

Yes, eslint also sends minimal changes. BTW, eslint implementation should give LSP compatible change chunks so it has advantage over more generic diff libraries. Just needs to be rewritten in...

Created Sublime Text issue for it here: https://github.com/sublimehq/sublime_text/issues/4084

Realistically also `lsp_utils` and `sublime_lib` would have to be updated or most of the LSP-* packages won't work. I only really use `ResourcePath` from `sublime_lib` so I could vendor it...

Node-based servers (or Microsoft's LSP library rather) have a code that force-kills the server if the parent process dies. So that covers the case when ST is closed and the...