3 ms·

I already use use-package, so that's great... I also use projectile and it's been working great... how should I prepare to move to project.el? Are there any gui

by brabel 4y ago

I already use use-package, so that's great... I also use projectile and it's been working great... how should I prepare to move to project.el? Are there any guides? Or things just work the same I am used to, and I just need to delete projectile once upgrading? I also use lsp-* for all IDE features... is eglot going to be the better choice here for every language?? LSP works with Go, Dart, Java, Zig, Rust, Lua... do I need to remove all my config for those to use eglot??

chimprich 4y ago
> how should I prepare to move to project.el? Are there any guides? # I recently switched from projectile to project and I noticed essentially zero changes. If you're not doing anything particularly custom you might not even notice. https://www.gnu.org/software/emacs/manual/html_node/emacs/Project-File-Commands.html https://www.gnu.org/software/emacs/manual/html_node/emacs/Pr...
- juxtapose 4y ago
  I tried switching to project.el, but eventually decided it's too bare-bones for me. As far as I'm concerned, project.el lacks the following features OOTB: 1. Something like the .projectile file to mark a folder as a project (without VCS). 2. Support for ag, rg and vterm. 3. Register new project types (to customize configure commands, compile commands, etc.) 4. Regenerate tags. 5. The ability to find the "other file" (x.h <-> x.c) across the project. And this list is incomplete! So if you rely on any of the above, I suggest not migrating to a project.el-only setup.
josteink 4y ago
> I also use lsp-* for all IDE features... is eglot going to be the better choice here for every language?? LSP works with Go, Dart, Java, Zig, Rust, Lua... do I need to remove all my config for those to use eglot?? eglot is just another (awkwardly named) lsp-client. It uses the exact same servers as lsp-mode does. You’ll need to adapt some hooks and key-bindings, but in terms of capabilities you shouldn’t be losing out.

by brabel 4y ago

chimprich 4y ago

> how should I prepare to move to project.el? Are there any guides? # I recently switched from projectile to project and I noticed essentially zero changes. If you're not doing anything particularly custom you might not even notice. https://www.gnu.org/software/emacs/manual/html_node/emacs/Project-File-Commands.html https://www.gnu.org/software/emacs/manual/html_node/emacs/Pr...

juxtapose 4y ago
I tried switching to project.el, but eventually decided it's too bare-bones for me. As far as I'm concerned, project.el lacks the following features OOTB: 1. Something like the .projectile file to mark a folder as a project (without VCS). 2. Support for ag, rg and vterm. 3. Register new project types (to customize configure commands, compile commands, etc.) 4. Regenerate tags. 5. The ability to find the "other file" (x.h <-> x.c) across the project. And this list is incomplete! So if you rely on any of the above, I suggest not migrating to a project.el-only setup.

josteink 4y ago

> I also use lsp-* for all IDE features... is eglot going to be the better choice here for every language?? LSP works with Go, Dart, Java, Zig, Rust, Lua... do I need to remove all my config for those to use eglot?? eglot is just another (awkwardly named) lsp-client. It uses the exact same servers as lsp-mode does. You’ll need to adapt some hooks and key-bindings, but in terms of capabilities you shouldn’t be losing out.