lsp-mode

This is a good point, but I do want to mention that I feel like in the past 5 years we've had lots of extremely popular packages that hook into Emacs internals instead of rolling out their own architecture. For example, corfu [0] versus company [1]. Company works with capf, but you can also write your own backends for it (specific to company). Corfu also works with capf, but all backends are capf functions instead of a corfu specific backend. Another good example is eglot [2] versus lsp-mode [3]. Eglot is actually packaged with Emacs now. There's also other stuff, like vertico [4] (and others that are recommended to download) versus helm/ivy. I also want to mention that packages that hook into Emacs more don't necessarily mean that they're better. From my POV it's more like you get a lot more things for free and the documentation you dive

I think lsp integration[0] can get you pretty far, but also if you use LLM features a la Copilot, I use ellama[1] for that. If there are other features you think you will miss, maybe I can ease your mind about those as well :) [0] https://github.com/emacs-lsp/lsp-mode [1] https://github.com/s-kostyaev/ellama

Thanks, for people looking for bug, see https://github.com/emacs-lsp/lsp-mode/issues/2080

lsp-mode: https://github.com/emacs-lsp/lsp-mode/issues/2080

>Finally for LSP, I always recommend Eglot over LSP Mode, as Eglot is written by an Emacs contributor that has deep knowledge of Emacs and Emacs Lisp. LSP Mode is written by volunteers on Github, and the code is nowhere near as good. This isn't really true at all, but even if it was, lsp-mode has a larger scope and has many more features than eglot. It's also much more actively maintained/developed than eglot is. Anyways, most FOSS code is written by volunteers. I really don't think that's a great argument against a FOSS project. Also see: https://github.com/emacs-lsp/lsp-mode/graphs/contributors https://github.com/emacs-lsp/lsp-mode/pulse/monthly https://github.com/joaotavora/eglot/pulse/monthly

I've had a terrible experience with lsp-mode, gopls and Emacs 27. Minor issues like inconsistencies and CPU/RAM hogging that requires manual restarts, and the major one that made me stop using it is that Emacs would frequently crash when editing Go files. I reported this to lsp-mode, but they kicked the can over to Emacs[1], which I never bothered reporting. The fact this is now a combination of tools with no clear reporting path when something goes wrong is awful UX. Every few months I update the entire setup with hopes things improve, but eventually I always get the crashes. I would really like for this to work, as the DX when it does is great, but for me it's just not there yet. [1]: https://github.com/emacs-lsp/lsp-mode/issues/3242

Don't think out of the box, but https://github.com/emacs-lsp/lsp-mode works rather well with emacs 28 from my experience. Emacs "distros" such as Spacemacs and Doomemacs both make using it a nearly "out of the box" experience. (not supporting the editor/ide war troll, just trying to contribute some useful info here)

Tooling has been a weak point, but it's getting better. I've been having a pretty good time of late with nimlsp[1] plus Emacs and lsp-mode[2]. [1] https://github.com/PMunch/nimlsp#readme [2] https://github.com/emacs-lsp/lsp-mode#readme

Emacs does support LSP: https://github.com/emacs-lsp/lsp-mode

This is what lsp-mode does https://github.com/emacs-lsp/lsp-mode/blob/master/examples/h...

Yeah, LSP may be turning out to be a good example of Microsoft going back to EEE; with a twist, though: rather than embracing a pre-existing standard, they're proposing a new one https://github.com/emacs-lsp/lsp-mode/issues/1863#issuecomme...

Sure, here are some samples from the source. This is Eglot's code. Try and figure out what's happening in each of these passages: https://github.com/joaotavora/eglot/blob/master/eglot.el#L41... https://github.com/joaotavora/eglot/blob/master/eglot.el#L41... https://github.com/joaotavora/eglot/blob/master/eglot.el#L17... Contrast with lsp-mode: https://github.com/emacs-lsp/lsp-mode/blob/master/lsp-mode.e... https://github.com/emacs-lsp/lsp-mode/blob/master/lsp-mode.e... https://github.com/emacs-lsp/lsp-mode/blob/master/lsp-modeli... The lsp-mode code is a lot easier to follow, in my opinion. It's a lot clearer what's happening (although I can't say much about whether either are overabstracted which is admittedly a big concern. I haven't looked into that). I remember watching an argument between the original authors on Reddit a while back.

"The Emacs and Vim ... are outclassed by modern IDE" Outclassed in what way? Have you looked at LSP[1] and its support in Emacs[2], for instance? That's not to mention things like SLIME and paredit for Lispy languages, or the integration of the rest of the Emacs ecosystem in to your development environment, the ability to develop and configure all these development tools in Lisp instead of being forced to switch to some other language, etc. [1] - https://github.com/Microsoft/language-server-protocol/ [2] - https://github.com/emacs-lsp/lsp-mode/

There are multiple LSP clients though, there's lsp-mode [1] and eglot [2]. After trying out both, I prefer Eglot, mainly because I find it faster and less intrusive than lsp-mode. It also composes better with built-in packages, such as flymake . I use gopls and pyls as language servers. 1. https://github.com/emacs-lsp/lsp-mode 2. https://github.com/joaotavora/eglot

If you're willing to give Emacs another shot, check out LSP-mode [0]. It's an implementation of the language server protocol, the same tech that powers the autocomplete/jump-to-def/etc. in VS Code, and so it offers exactly the same functionality for all the same languages. It's true that it's not built into Emacs, but it's easy to set up and works well. It's been a total game changer for me - it's allowed me to transition to using Emacs full-time for professional Python programming. [0] https://github.com/emacs-lsp/lsp-mode