4 ms·
> Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client. It’s funny that you generally don’t nee
by blahgeek 2y ago
> Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client.
It’s funny that you generally don’t need to do that for editors like vim or emacs - only need to add a single line in config to specify the command line argument
- ratmice 2y agoIt honestly depends on how much your LSP server infests the editor. In the language server I wrote there are really 2 cases where we utilize the creation of an editor-specific extension * dynamic registration of file extensions * display of svg generated by the language server. We also had to write ad-hoc custom vim-script and would need to do the same for emacs for the first of those, and just dump a URL for vim to punt to a browser for the latter. But it isn't unrealistic to require a custom editor scripts for other editors besides vscode, in the sense that I've done so...
- bryjnar 2y agoIt depends - the client modules for Emacs' `lsp-mode` generally need a fair bit of configuration. Not just how to launch the server, but also often defining a native-compatible way of setting the options. e.g. for Emacs they often get wired up as `defcustom`s.