emacs-gcc-wayland-devel-builder VS python-lsp-server

I have nearly the same problem (just different displays), so I use a Wayland version of Emacs: https://github.com/mpsq/emacs-gcc-wayland-devel-builder

I use it on wayland without xwayland. You just have to build it natively. I'm on arch linux https://aur.archlinux.org/packages/emacs-gcc-wayland-devel-bin

Installed wayland build of emacs from here. Seems to work a little better.

Is there a way to detect if my emacs was compiled with native json support? I'm using the pgtk3 emacs from here: https://github.com/mpsq/emacs-gcc-wayland-devel-builder, and experiencing the same slowness with lsp-ui-doc-mode.

For me it works also on AUR emacs-gcc-wayland-devel-bin build

AUR https://aur.archlinux.org/packages/emacs-gcc-wayland-devel-bin/

I managed to fix this by rolling back Emacs to before when was made mandatory (this is the specific repo & release that worked for me on Arch).

Python LSP Server works great, is easier to install and even offers some optional extensions.

https://github.com/python-lsp/python-lsp-server

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

I came at the tail end of https://github.com/python-lsp/python-lsp-server/issues/195. The possibility of me sponsoring a fix came up, and I’m on board with it, but the other contributor never replied.

I haven't used pylint, but I find mypy with python-lsp-server extremely easy to use with nvim-lspconfig, especially on Arch linux.

Whatever you use, make sure you have syntax highlighting, completion and error checking! I'm using pylsp and shellcheck in emacs, but those or similar options should work in any IDE, replacing much of what made IDEs unique in former times.

Perhaps unrelated, from my experience, pylsp is better than pyright, see https://github.com/python-lsp/python-lsp-server/.

I am finally starting to use lsp for python development. I am using pylsp as LS.

I'm talking about this python LSP server (the command is pylsp that's why).

Another example, you can setup python-lsp-server with nvim-lspconfig (lsp server also needs to be installed globally or in virtualenv) and they have a plugin for black which you can then install in the same virtualenv and just use lsp to format the code instead of formatter.nvim.

Do you use any lsp (like pylsp or pyright)? If yes, did you setup it to use proper python / did you activate venv?