sublime text sftp set up new server not working

The docs were vague, and I think I had to put some JSON configuration structure in some file, but nothing I tried I guess was the right file or right structure. I figured LSP would help in this regard, but I couldn't make it work. The symbols, if I understand correctly, are based on the syntax configuration, and for the common Elixir one, it includes the type definition line, each function head, and the callsites of the function, which makes it nearly useless for symbol navigation. The sort of minimal deal breaker level of support for me is being able to jump to definition. I figured I'd wait until the non beta release, and try again. I couldn't get the LSP to work for me for Elixir, so I ended up back on VSCode for now.

I was formerly a paid user of ST3 before switching to VSCode, but gave the ST4 beta a try a month or so ago. It allows ST users to contribute to the LSP plugin, while ST devs can focus on making ST more awesome on their own way and adding new API-s.Īll I can say is that LSP already has first class support, because the ST devs have specifically expanded the API to allow LSP to implement certain features. Having LSP as a plugin allows the best for both ST users and ST devs. So ST would chase after offering the same functionality as VS Code, but then always be a step back. ST devs would shift focus on implementing the LSP spec which is mainly driven by Microsoft and the spec is somewhat driven by VS Code functionality. The speed mostly depends on the speed a language server returns a response to the LSP client. Implementing the LSP client in c++ won't make the user experience faster. That would mean that the LSP source code would be closed source too and that would not allow other people to contribute to it. Just wanted to share my thoughts on why LSP as an open source plugin has more benefits than getting first class support from ST devs.Ĭons of getting first class support from ST:

Sublime text sftp set up new server not working