#lspmode — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lspmode, aggregated by home.social.
-
Spent the morning replacing lsp-mode with Eglot due to slop code in the former.
Seems to have gone smoothly, I'm really enjoying the snappiness of it, using lsp-mode by comparison is like wading through molasses.
Am using the following:
* java-language-server as the LSP language server, which is blazingly fast
* company-mode for completions
* breadcrumb-mode for headerbar navigationThings I'm missing still (suggestions welcome!):
* auto-import (this may be a limitation of the LSP impl?)
* a context menu for jumping to declarations at point
* flymake error/warning/info summary in dired mode -
-
Delighted to find that Emacs' `lsp-mode` package already has support for the Python type-checker `ty` (it was merged back in May https://github.com/emacs-lsp/lsp-mode/pull/4785). If you've got it installed in your virtual environment then it may well "Just Work(tm)" out of the box when you next open a file in your project (it did for me).
Emacs and its users, package developers, contributors never ceases to amaze and please me.
-
getting rather fed up of `lsp-mode`continually offering to install `copilot-lsp` for me whenever I open a buffer for which there isn't a language server.
I found the thread
https://github.com/emacs-lsp/lsp-mode/pull/4635#issuecomment-2563163891
..and have set `lsp-copilot-applicable-fn` to the recommended `lambda`function and `lsp-copilot-enabled` is set to `0` but still I get asked!.
Very annoying.
-
@pkw #Eglot and #lspmode are #LSP clients for #Emacs, use either or. Eglot is built-into Emacs 29 and upwards and is meant to integrate with existing Emacs utilities, LSP-mode has some more bells and whistles. I found I don't need those and use Eglot. As the language server I use #pylsp, which by default uses the #jedi Python package for completion. You don't need a jedi-specific Emacs package anymore if you use LSP, but still should install the Python package.
-
@pkw #Eglot and #lspmode are #LSP clients for #Emacs, use either or. Eglot is built-into Emacs 29 and upwards and is meant to integrate with existing Emacs utilities, LSP-mode has some more bells and whistles. I found I don't need those and use Eglot. As the language server I use #pylsp, which by default uses the #jedi Python package for completion. You don't need a jedi-specific Emacs package anymore if you use LSP, but still should install the Python package.
-
@pkw #Eglot and #lspmode are #LSP clients for #Emacs, use either or. Eglot is built-into Emacs 29 and upwards and is meant to integrate with existing Emacs utilities, LSP-mode has some more bells and whistles. I found I don't need those and use Eglot. As the language server I use #pylsp, which by default uses the #jedi Python package for completion. You don't need a jedi-specific Emacs package anymore if you use LSP, but still should install the Python package.
-
@pkw #Eglot and #lspmode are #LSP clients for #Emacs, use either or. Eglot is built-into Emacs 29 and upwards and is meant to integrate with existing Emacs utilities, LSP-mode has some more bells and whistles. I found I don't need those and use Eglot. As the language server I use #pylsp, which by default uses the #jedi Python package for completion. You don't need a jedi-specific Emacs package anymore if you use LSP, but still should install the Python package.
-
@pkw #Eglot and #lspmode are #LSP clients for #Emacs, use either or. Eglot is built-into Emacs 29 and upwards and is meant to integrate with existing Emacs utilities, LSP-mode has some more bells and whistles. I found I don't need those and use Eglot. As the language server I use #pylsp, which by default uses the #jedi Python package for completion. You don't need a jedi-specific Emacs package anymore if you use LSP, but still should install the Python package.
-
Show me your cool @[email protected] config.el and I’ll send you a sticker!
Bonus points for awesome #orgmode and #lspmode hooks
Stickers thanks to @[email protected]