491–500 of 539 posts
Earlier quoted context omitted.
Same here. 20 years, Europe, corporate and open source projects, zero emacs users. Seen vim, notepad++, sublime, uedit, atom and vscode. And all types of fat ides
Yeah, we European Emacs users went to the states to earn real money :^)
Earlier quoted context omitted.
It would be bad if it did, IMO. Eglot is a pretty dodgy piece of software and the code is much worse than lsp-mode.
Could you give some justification for that criticism and assertion please? (On its own, your comment falls short of HN standards.)
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 lsp-mode author came across as... let's just say more professional. lsp-mode seems much closer to a professional product to me in general.
Earlier quoted context omitted.
> No amount of crippling Emacs would help there. It can only spoil it for existing happy users. I am surely against "crippling." The initial topic of the discussion was how to make Emacs accessible to the new users. I don't suggest making fixed changes to anything, only allowing somebody to easily select different defaults which correspond with the keyboards available today. Today's keyboard has no meta key. Old keyb…
But that is certainly not only possible, but available today in Emacs. It's here. Use it and evangelize it if you like.
Earlier quoted context omitted.
Is the LSP architecture the way to go, though? In my experience it's quite a bit slower than built in emacs modes. I can't use tools that are slower than me.
Are you on Emacs 27 yet? Below that Emacs encodes JSON in Elisp, which is extremely slow and makes LSP unusable.
Earlier quoted context omitted.
Could you give some justification for that criticism and assertion please? (On its own, your comment falls short of HN standards.)
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://gi…
Eglot: 70 open, 277 closed
lsp-mode: 94 open, 977 closed
(lsp-mode is much more than 3x the size of eglot and has 15x the number of downloads on MELPA)
Earlier quoted context omitted.
YMMV, out of hundreds emacs packages I use, I remember issues installing exactly one package. For comparison, I easily remember issues with more than deb package on Ubuntu and I consider apt-get ecosystem as pretty reliable.
How and what do you use for package management on emacs?
(use-package which-key
:config
(which-key-mode))
Historically, el-get e.g.:
(el-get-bundle ace-link)
Earlier quoted context omitted.
Are you on Emacs 27 yet? Below that Emacs encodes JSON in Elisp, which is extremely slow and makes LSP unusable.
Upgrading to 27 made no difference for me.
https://emacs-lsp.github.io/lsp-mode/page/performance/
Ordinarily I'd ignore rabbit holes like this but LSP is unusually useful. It's worth a shot.