![]() ![]() In any case, the setup described here is still far superior to not using anything other than projectile and ripgrep so I am satisfied for now. However, that probably has a lot more to do with TRAMP than any of the language servers, and in any case Magit still makes emacs far superior. ConclusionsĮmbarrassingly, neither setup provided as pleasant an SSH based workflow as VS Code. Where you will need to replace "blah" with the output of (system-name). Essentially we have the following Rosetta stone.ġ ( after! eglot 2 :config 3 ( add-hook 'nix-mode-hook 'eglot-ensure ) 4 ( add-hook 'f90-mode-hook 'eglot-ensure ) 5 ( set-eglot-client! 'cc-mode ' ( "clangd" "-j=3" "-clang-tidy" )) 6 ( set-eglot-client! 'python-mode ' ( "pylsp" )) 7 ( when ( string= ( system-name ) "blah" ) 8 ( setq exec-path ( append exec-path ' ( 9 ( concat ( getenv "HOME" ) "/.micromamba/envs/lsp/bin/" ) python, fortran 10 ( concat ( getenv "HOME" ) "/.local/lsp/bin/" ) clangd 11 ( concat ( getenv "HOME" ) "/.digestif/bin/" ) tex 12 ( concat ( getenv "HOME" ) "/.nvm/versions/node/v16.1.0/bin/bash-language-server" ) 13 ))) 14 ) 15 ) Language Serversįor getting the language server providers themselves, we will mostly leverage direct binaries where possible, but also, depending on the implementation, virtual environments 3. I’m more interested in working with doom-emacs than vanilla emacs and so am pretty invested in non-core libraries like projectile 2. This is great, and a good direction for the project to grow in, but it constrains my workflow unnecessarily. Overall the main issue with eglot seems to be the insistence to be accepted into emacs core someday. ![]()
0 Comments
Leave a Reply. |