Great article! I'm currently using doom + lsp-mode with ts-lsp and tailwindcss-lsp. It works great, but as the author said the performance could be better, especially tailwindcss-lsp which routinely freezes emacs on longer classnames.
Does anyone know if I can use this setup with doom, or will there be any issues in regards to config conflicts? I don't want to leave the convenience of doom for other things.
…I hardly ever run into any performance issues anymore with lsp when using that. The author mentions it, and I use it with Doom every day with minimal issues.
Comments
Great article! I'm currently using doom + lsp-mode with ts-lsp and tailwindcss-lsp. It works great, but as the author said the performance could be better, especially tailwindcss-lsp which routinely freezes emacs on longer classnames. Does anyone know if I can use this setup with doom, or will there be any issues in regards to config conflicts? I don't want to leave the convenience of doom for other things.
You can go and use: https://github.com/blahgeek/emacs-lsp-booster
…I hardly ever run into any performance issues anymore with lsp when using that. The author mentions it, and I use it with Doom every day with minimal issues.
What’s the use of this package? Isn’t Treesitter built in Emacs (at least if compiled with tree sitter support)?
It's like a scope for your config. I often do the same to group settings per-package, e.g. for dired.