Our great sponsors
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
https://github.com/hrsh7th/nvim-cmp
No different than installing plugins in VSCode for completions, they all work via the same protocl https://microsoft.github.io/language-server-protocol/
https://github.com/hrsh7th/nvim-cmp
No different than installing plugins in VSCode for completions, they all work via the same protocl https://microsoft.github.io/language-server-protocol/
I love emacs, but agree with many of your criticisms.
Emacs can be slow. I don't use LSP, so can't comment on that, but it's definitely slow on long lines with syntax highlighting.
I don't use TRAMP for exactly one of the reasons you mentioned: it can hang Emacs. I want to avoid that at all costs, because I pretty much live in Emacs.
Handling buffers is tedious, but you can improve that through various packages, like popper[1]
Depending on what problems you run in to and your skill level, it could be tricky to debug elisp programs. However, compare that to when you run in to some bug in VSCode... how are you going to debug that? You'll probably have to submit a bug report and wait for the developers to get to it (if they ever do)... how is that better than emacs?
Also, remember that you don't have to go it alone in troubleshooting the issues you run in to with emacs. There's a whole community ready and willing to help.
Despite the downsides of emacs, I still use and love it. Every editor has downsides, and emacs is no exception. Its positives far, far outweigh the negatives for me. There's just so much more that it can do than other editors, and it's far more customizable. I very much doubt I'll ever seriously consider switching to another.
[1] - https://github.com/karthink/popper
Yep. You can use flymake or flycheck for that in combination with eglot or lsp-mode.
See https://github.com/joaotavora/eglot#diagnostics
I just stopped worry and succumbed to https://github.com/emacs-evil/evil.
> or an implementation that runs on bare metal
There's https://github.com/whily/yalo apparently
While I wholeheartedly agree, you don't have to sprinkle Lua everywhere, you can use both. As a matter of fact, I do[0]. And when I want to enable a setting on the fly in the editor, I still use the vimscript version. But Lua is way nicer to work with the moment you do something non trivial. For example, I've never been able to make sense out of vimscript string interpolation.
0: https://github.com/RMPR/dotfiles/blob/master/.config/nvim/in...