Rafał Chłodnicki

Looks like it turned out to be a language server issue: https://github.com/python-lsp/python-lsp-server/issues/121#issuecomment-979344262

It looks a bit rough code-quality wise but thanks, it can be polished before merging. High-level question to @rwols, @predragnikolic, do you prefer explicit config option for enabling node-ipc or...

I would think something like `"transport": "..."` but that would be a breaking change for the `tcp` case which currently doesn't require this new option to be set. So just...

Have you verified that it still works when not using `use_node_ipc`? I see some weird crashes without even using it but don't have time to investigate right now.

Then I would try to make changes here so that it's not a breaking change for chokidar watcher. Maybe possible by making the newly added arguments optional. Watcher is using...

Alternatively, if the former would be too messy, we can update the watcher to use the new API but it should be done in a way that supports both new...

Again, don't have time to investigate right now, but it appears to break LSP-chokidar, even when not using any of this functionality explicitly. No didChangeWatchedFiles notifications trigger anymore. EDIT: Actually...

Added - LSP-typescript issue: https://github.com/sublimelsp/LSP-typescript/issues/129 - Upstream issue: https://github.com/sublimehq/sublime_text/issues/3796

If it shows up in the lower-left corner of ST window then it means it's working. It's just a matter of configuring eslint through project-specific eslint configuration to make it...

are you able to provide a github repository that reproduces the issue?