3 ms·

Are you sure? I could have sworn my lsp-mode uses at least flymake, xref, and projectile (which I use over project.el) as well, and I don’t remember making a cu

by anyfoo 4y ago

Are you sure? I could have sworn my lsp-mode uses at least flymake, xref, and projectile (which I use over project.el) as well, and I don’t remember making a custom setup in that regard? Not in front of emacs right now, but very sure. Maybe that was different in the past? I switched from eglot back to lsp-mode a while ago, but I don’t quite remember why unfortunately. I think lsp-mode “did more” or something like that, and seemed to have changed for the better.

tptacek 4y ago
I just remember a zillion weird popups with lsp-mode, which is all UI that isn't built in to Emacs. But also: Projectile isn't built into Emacs. Project.el is. The lsp-mode hovers are bespoke; eglot just uses ElDoc. lsp-mode wants you to use flycheck; flycheck isn't built into Emacs. lsp-mode can use xref, but it also has its own thing. lsp-mode has its own header and modeline goo. It goes on like that. None of this is bad. These aren't critiques of lsp-mode. But they're definitely reasons why it would make sense to integrate Eglot, which prioritizes integrating with Emacs built-in libraries. The actual critique of lsp-mode I would make is that I bounced from lsp-mode at least 3 times trying to get things working, and things would always be ok for like a couple days and then I'd lose 30 minutes to debugging and ultimately just turn it all off so I could get on with my day. I enabled Eglot once, with like 10 lines of use-package, and haven't touched it since.
- josteink 4y ago
  > I just remember a zillion weird popups with lsp-mode I think that may be lsp-ui, not lsp-mode, but I might be mistaken.
- anyfoo 4y ago
  Sorry, I’m just not sure most of that is true anymore. How long ago was your experience? I remember bouncing off lsp-mode into eglot years ago as well for similar reasons, but nowadays it just seems totally different to me. I’ve never used anything but xref in lsp-mode, I rely on xref a lot. I wasn’t even aware that lsp-mode has, or had, something bespoke there. I use flymake, not flycheck, I don’t think I had to configure that. projectile is just my personal preference because I'm used to it, the manual says it integrates with either project.el or projectile. I remember the weird popups you mention from my first lsp-mode trial. I don’t know where they’re gone, nowadays it’s just text in the buffer. (But I don’t know whether that’s ElDoc or not.)
- deleted 4y ago
  [deleted]
- Myrmornis 4y ago
  Yes I had exactly the same experience, maybe 3 years ago? Installing lsp-mode resulted in an overblown UI with all sorts of gadgets; it looked like an attempt to create an "IDE experience" in Emacs, and so I ran away, used eglot for a few months, and then ended my 20-year Emacs run and switched to VSCode. (Apart from magit -- of course I do still have an Emacs instance running.) But it does sound like people are saying that lsp-mode got rid of the tasteless stuff. And since Eglot development has now moved away from GitHub to a combination of unpleasant mailing lists and unfashionable issue-tracking apps, I wonder whether it will stand a chance in the future competition.
  - solomatov 4y ago
    There's a magit like extension for vscode: https://marketplace.visualstudio.com/items?itemName=kahole.magit https://marketplace.visualstudio.com/items?itemName=kahole.m...

by anyfoo 4y ago

tptacek 4y ago

I just remember a zillion weird popups with lsp-mode, which is all UI that isn't built in to Emacs. But also: Projectile isn't built into Emacs. Project.el is. The lsp-mode hovers are bespoke; eglot just uses ElDoc. lsp-mode wants you to use flycheck; flycheck isn't built into Emacs. lsp-mode can use xref, but it also has its own thing. lsp-mode has its own header and modeline goo. It goes on like that. None of this is bad. These aren't critiques of lsp-mode. But they're definitely reasons why it would make sense to integrate Eglot, which prioritizes integrating with Emacs built-in libraries. The actual critique of lsp-mode I would make is that I bounced from lsp-mode at least 3 times trying to get things working, and things would always be ok for like a couple days and then I'd lose 30 minutes to debugging and ultimately just turn it all off so I could get on with my day. I enabled Eglot once, with like 10 lines of use-package, and haven't touched it since.

josteink 4y ago
> I just remember a zillion weird popups with lsp-mode I think that may be lsp-ui, not lsp-mode, but I might be mistaken.
anyfoo 4y ago
Sorry, I’m just not sure most of that is true anymore. How long ago was your experience? I remember bouncing off lsp-mode into eglot years ago as well for similar reasons, but nowadays it just seems totally different to me. I’ve never used anything but xref in lsp-mode, I rely on xref a lot. I wasn’t even aware that lsp-mode has, or had, something bespoke there. I use flymake, not flycheck, I don’t think I had to configure that. projectile is just my personal preference because I'm used to it, the manual says it integrates with either project.el or projectile. I remember the weird popups you mention from my first lsp-mode trial. I don’t know where they’re gone, nowadays it’s just text in the buffer. (But I don’t know whether that’s ElDoc or not.)
deleted 4y ago
[deleted]
Myrmornis 4y ago
Yes I had exactly the same experience, maybe 3 years ago? Installing lsp-mode resulted in an overblown UI with all sorts of gadgets; it looked like an attempt to create an "IDE experience" in Emacs, and so I ran away, used eglot for a few months, and then ended my 20-year Emacs run and switched to VSCode. (Apart from magit -- of course I do still have an Emacs instance running.) But it does sound like people are saying that lsp-mode got rid of the tasteless stuff. And since Eglot development has now moved away from GitHub to a combination of unpleasant mailing lists and unfashionable issue-tracking apps, I wonder whether it will stand a chance in the future competition.
- solomatov 4y ago
  There's a magit like extension for vscode: https://marketplace.visualstudio.com/items?itemName=kahole.magit https://marketplace.visualstudio.com/items?itemName=kahole.m...