[sreevisakh]

I used lsp-mode for a while and then switched to eglot. The reason was that lsp-mode has quite a lot of dependencies including helm and hydra. This can be inconvenient when you use their alternatives likes the vertico-corfu stack. I didn't want more than one extension of the same type in my configuration. eglot uses native emacs APIs for completions and tooltips. This integrates very well with vertico and corfu.

> Also I wonder: if eglot is now part of Emacs, is there any incentive for the lsp-mode devs to keep working on lsp-mode?

I'm pretty sure that some people will stick to lsp-mode. There are a few builtin extensions which I replaced with more popular external packages (eg: projectile vs project.el). So, I think the lsp-mode devs should keep at it.

[jacobsenscott]

lsp-mode does not depend on helm or hydra, or anything else really. There are optional packages that allow it to work better with those systems though.

https://emacs-lsp.github.io/lsp-mode/page/installation/#vani...

[aardvark179]

Lsp mode depends on neither helm, nor hydra. I think there are some utility things that can use helm, but as far as I remember it that didn’t require that helm was set up for anything else and it has never conflicted with anything else I use.

[wakeupcall]

> (eg: projectile vs project.el).

Always curious of why you prefer one of the other. Any major thing you prefer projectile? (only ever used project.el here and was satisfied)

Similarly, I'm using ivy, first time I see vertico which looks similar.

[ghosty141]

It has a working switch to cpp/hpp function that you cant really get otherwise. Thats the only thing I miss from projectile.

[mickeyp]

This is actually a builtin feature of Emacs, and is available regardless of whether you use projectile or project.

Try `M-x ffap' whilst point is on an include directive's filename, or `M-x ff-find-other-file' to jump between C/H header files.