4 ms·

I'm a big fan of Vim, but I hardly use it as my primary editor anymore (applies for Neovim as well). I think the ecosystem is amazing, but I hardly have the pa

I'm a big fan of Vim, but I hardly use it as my primary editor anymore (applies for Neovim as well). I think the ecosystem is amazing, but I hardly have the patience to set things up to feature parity with other editors. Debuggers are the biggest missing/hard to configure feature. I do, however, use Vim bindings in every editor that supports them (and extensions for browsers like Vimium). The extensions/Editor functionality are hit-or-miss; some are missing key bindings that I use often, or features don't quite work correctly, but I find it much more enjoyable to use than the "typical" approach. The VSCode one is pretty good (even has EasyMotion/Sneak out of the box, if that's your style), but often seems to slow down and buffer keystrokes on heavy load/undo seems very hit or miss.

emresahin 2y ago
Did you try Lazyvim?
- Shadowmist 2y ago
  Naw it is too much effort to set up.
  - lawn 2y ago
    I've seen many takes on these "NeoVim distros", but them being too much effort is new.
stevekemp 2y ago
For 20+ years I did all my coding, development, and miscellaneous tasks in Emacs. But I used vim exclusively for writing emails - initially with mutt, and later with different mail clients. There were times, now and again, where I'd use vi, or vim, on solaris, or other "weird" systems. But basically I used vim for emails and emacs for everything else, and I think that was a good split. Were I telling somebody to start a new editor these days I think I'd probably echo the recommendation to use the integrated tutorial, but after that just "jump in". gvim, emacs, and similar have menubars that help with many things before you learn the keystrokes required and there's no shame in using them. The article suggests learning and experimenting before switching, but to me that seems very counter-intuitive.
phatskat 2y ago
Mason brings a lot of what I needed for LSP, and their DAP servers are getting better. Debugging in (n)vim will likely remain a fun trudge for a while but it is getting better. I found a lot of issues with trying to get a “good” setup, or got frustrated that moving from one job to another meant attempting to port my working setup to a new machine and new projects. I recently went back to NvChad and have done almost no custom config and I love it.
worksonmine 2y ago
> Debuggers are the biggest missing/hard to configure feature. Do you know about :termdebug and what are you missing with it? It's just dbg hooked into vim, and you can use any other compatible debugger instead if you prefer, for example rr. That's the beauty of vim, the tools you use are the tools you'd use in your terminal anyway.
- nyarlathotep_ 2y ago
  I did not, this is interesting. I'll look into this, thanks!

emresahin 2y ago

Did you try Lazyvim?

Shadowmist 2y ago
Naw it is too much effort to set up.
- lawn 2y ago
  I've seen many takes on these "NeoVim distros", but them being too much effort is new.

stevekemp 2y ago

For 20+ years I did all my coding, development, and miscellaneous tasks in Emacs. But I used vim exclusively for writing emails - initially with mutt, and later with different mail clients. There were times, now and again, where I'd use vi, or vim, on solaris, or other "weird" systems. But basically I used vim for emails and emacs for everything else, and I think that was a good split. Were I telling somebody to start a new editor these days I think I'd probably echo the recommendation to use the integrated tutorial, but after that just "jump in". gvim, emacs, and similar have menubars that help with many things before you learn the keystrokes required and there's no shame in using them. The article suggests learning and experimenting before switching, but to me that seems very counter-intuitive.

phatskat 2y ago

Mason brings a lot of what I needed for LSP, and their DAP servers are getting better. Debugging in (n)vim will likely remain a fun trudge for a while but it is getting better. I found a lot of issues with trying to get a “good” setup, or got frustrated that moving from one job to another meant attempting to port my working setup to a new machine and new projects. I recently went back to NvChad and have done almost no custom config and I love it.

worksonmine 2y ago

> Debuggers are the biggest missing/hard to configure feature. Do you know about :termdebug and what are you missing with it? It's just dbg hooked into vim, and you can use any other compatible debugger instead if you prefer, for example rr. That's the beauty of vim, the tools you use are the tools you'd use in your terminal anyway.

nyarlathotep_ 2y ago
I did not, this is interesting. I'll look into this, thanks!