51–60 of 106 posts
I've really tried to move from vim to neovim for a long time and spent many hours trying to configure it to behave like vim, but every time I try it breaks in unexpected ways or it hungs up, while vim for my workflow never flinks. I hope that they'll reach a 1.0 soon where things are more stable.
nvim: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by nvim)
Why binary doesn't support old glibc?
How 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.
1. https://launchpad.net/~neovim-ppa/+archive/ubuntu/stable 2. https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable
I 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…
There are different defaults for the pane management and the terminal. The vim defaults, IMO, allow a more consistent user experience. E.g. when you are in a vim terminal and you go to normal mode to yank some stuff to put it in the other pane with the code, nvim defaults adds line numbers to the terminal that need to be cleaned up afterwards, vim just does not add them. This is just one small example, but there are several edge cases where the vim defaults behave like I would expect and nvim either does something unexpected or it lags or it crashes.
I have tried many times to switch to Neovim, but I keep coming back to VS Code. 1. I can't create configs myself. 2. Astro, Lunar ... all break at sometime.
Start small with empty config and no plugins and search the web when ever you want to do things. Yes at first it feels strange and even stupid that you search replace with '%s/oldword/newword/gc'. Then you realize sed in the terminal is the same syntax, 'sed s/old/new/g' and things start to click.
Once you're comfortable you know what you want out of the tool and what features you'd like to add. Chances are you'll find completely new ways of doing things with much more flexibility so don't limit yourself to the plugins too early. The only plugins I use today is fzf, and nvim-lspconfig.
I have tried many times to switch to Neovim, but I keep coming back to VS Code. 1. I can't create configs myself. 2. Astro, Lunar ... all break at sometime.
Agreed. Neither VS Code nor VS Codium (my preferred variant, telemetry-free) have ever broken my setup with an update, something I can’t say about NeoVim or Emacs.
Telemetry reduced -
https://github.com/VSCodium/vscodium/blob/master/DOCS.md#dis...
How 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.
PPAs are available for both stable (0.7.x)[1] and unstable (this 0.9)[2] versions. I use the latter and it has worked well for me. 1. https://launchpad.net/~neovim-ppa/+archive/ubuntu/stable 2. https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable
I 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.…
Some of the VS Code extensions provide some nice added value, such as LLDB debugging for C/C++ and Rust, but you can actually get this in Neovim, you just need to install the extension in VS Code and then point to it from Neovim. If you dig around, you can see this in my dotfiles, linked in another comment. And this is only an issue for debugging compiled code to give nicer variable information for e.g. strings, which is quite specific.
I've also found Microsoft's recent move to Pylance from Pyright has meant a few small things aren't there for Python, which admittedly was disappointed, but again, broadly this isn't an issue at all.
Otherwise, I've not found this issue with Neovim at all.
I 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.…
Most of the time we edit code, not write it. And this is where (neo)vim shines. You can move between places you want to modify and do so with as little afford as possible.
Language support (at least for languages I use the most) is the same as VSCode and IDEA (give or take) but at least I get to decide what do I want to get from the tool.
>People praise vim/neovim for being small but to get any decent functionality you will end up with tons of plugins.
No, these days you basically need only a plugin manager + treesitter + LSP (add a few UI plugins to your taste).