Does anyone have a TLDR/highlights of the release?
Neovim 0.9
11–20 of 106 posts
Re: Neovim 0.9
#12I'll kind of hijack this thread to ask a support question:
I often use neovim within the terminal in VSCode. Lately, I've had issues with the cursor becoming invisible while in normal mode. The line cursor works as expected in insert mode. Changing the settings for cursor style in VSCode temporarily fixes it, but the problem comes right back when I transition to insert mode and come back to normal mode. Anyone have any suggestions for a fix?
Re: Neovim 0.9
#13[deleted]
Re: Neovim 0.9
#14I began utilizing Vim approximately three decades ago, and experiencing a contemporary tool like Neovim still feels incredibly astounding.
As a counterpoint of sorts, if you are accustomed to vim, moving to neovim entails almost zero switching friction.
Everything works just like it's supposed to. In fact sometimes I get neovim instead of vim (when I run "vi" from the shell) and I don't even notice.
I have a fairly simple vim config.
I'm sure this means that I'm missing out on all the great new things about neovim, and maybe I'll get there some day. But I am happy with how vi/vim/neovim work reliably and consistently every time.
Re: Neovim 0.9
#15> EditorConfig support is now builtin.
That's great, one less plugin to install.
Re: Neovim 0.9
#16Does anyone have a TLDR/highlights of the release?
Re: Neovim 0.9
#17For people who have used helix and neovim recently, how do they compare?
Stating the obvious - the edit modes are fundamentally different and helix doesn't have a plugin ecosystem yet. Helix uses the kakoune model: vi basic grammar is verb followed by object; it’s nice because it matches well with the order we use in English, "delete word". On the other hand, it does not match well with the nature of what we express: There is only a handful of verbs in text editing (delete, yank, paste, i…
This is a great point, although of course vim does let you visually select before verbing a chunk of text. Useful for cases where your object spec doesn't fit into the easy categories of character/word/block/etc.
I'm not familiar with the Kakoune or Helix selection UX, but it's keystroke-economical in vim (of course).
Re: Neovim 0.9
#18How do you all install neovim on Linux? The .deb is gone with this release, which I think was the most orderly way to fit into my install. I think I'll want to find a PPA solution now. I am not a fan of installs that are not reversible.
Re: Neovim 0.9
#19I spent a good amount of time learning vim/neovim and installed tons of plugins, but in the end I didn't see the point. Language support is still nowhere near VSCode, let alone Jetbrains products. I do all my development on a macbook so ultra low memory or being installed by default is not a requirement.
People praise vim/neovim for being small but to get any decent functionality you will end up with tons of plugins. The default vim/neovim is a fine text editor but when you need to write text you have better tools anyways. Maybe one can type fast in vim, but who is writing code limited by the speed of typing.
Re: Neovim 0.9
#20For people who have used helix and neovim recently, how do they compare?
Stating the obvious - the edit modes are fundamentally different and helix doesn't have a plugin ecosystem yet. Helix uses the kakoune model: vi basic grammar is verb followed by object; it’s nice because it matches well with the order we use in English, "delete word". On the other hand, it does not match well with the nature of what we express: There is only a handful of verbs in text editing (delete, yank, paste, i…
How is this different than Vim's visual/visual-line/visual-block modes? Other than the mode now being the default behavior, that is.