lsp-tailwindcss VS apheleia

Of course, there's already a package for TailwindCSS using LSP. With Doom Emacs installation instructions as well!

As far as out-of-the-box support, I think it works great. Much easier to configure than lsp-mode.

However, for my uses with a Ruby/React+TSX setup the performance was lacking on a large codebase. I swapped back to lsp-mode and the experience felt smoother.

IIRC the author's stance on previous discussions around multiple language servers was to rely on flymake instead, since the previous discussion centered around ESLint + TypeScript. Tailwind is a bit of an issue in the ecosystem right now, but you may want to try https://github.com/merrickluo/lsp-tailwindcss.

I am trying to use lsp-mode for ruby via solargraph and for Rails era templates using web-mode via lsp-tailwindcss and both seems to kinda sorta work but neither one is really giving me all the features that I see that others have.

There is https://github.com/merrickluo/lsp-tailwindcss and AFAIK it shows colors but Im not 100% sure. Need to check it when I'm back home.

This past September I reported to lsp-tailwindcss that their package somehow unbind C-c p p from projectile-switch-project, the developer was clueless since their package indeed does not define keys or anything, I had no remedy than deactivating it.

For black, I can recommend apheleia. It handles not only black but also all the other common formatters (not only for Python), with custom ones being relatively easy to add.

1.projectile-kill-buffers or the built-in project-kill-buffers will do that for the current project. You could run that before switching projects.

2. https://github.com/radian-software/apheleia

3. There might be a way to do this but I'm not sure. Emacs being inherently single threaded probably makes this difficult. But yes, I use M-x (re)compile.

4. libvterm is the best still imo. You can definitely do multiple instances and there's even different tab modes in Emacs now.

I forgot to mention a third option namely lassik/emacs-format-all-the-code and there are efforts to combine/consolidate the three into a single package which would be great.

raxid502/apheleia

I use formatters in order to automatically format source code on save. Personally I use apheleia for this. It requires clang-tools installed as it uses clang formatter.

Generally speaking, emacs does only so much for indenting those mixed mode files, so you might want to use a dedicated JS(X)-formatter (default one would be prettier). I can recommend integrating it using apheleia. It automatically prettifies buffers on save, but without having your cursor jump around like prettier-mode does. It also relies on having the prettier script available (from npm i -g prettier or its likes).