- use-package built in
- csharp-mode (now built in)
- typescript-mode (now built in)
- same with json-mode too.
- project.el instead of projectile
- eglot (now built in) over lsp-mode
As far as Emacs releases goes this one has more functionality packed than I can remember in any previous release ever.
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??
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/Pr...
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.
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.