Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neovim 0.9

github.com

Post reply on HN
Print view View original

71–80 of 106 posts

Re: Neovim 0.9

#71

Post by ilovecaching »

gpanders wrote: post #69
ilovecaching wrote: post #67

Earlier quoted context omitted.

I use default vim, I believe it was a mistake to fracture the ecosystem with plugins that can only be used with neovim. I have also not found any neovim functionality that sells neovim over vim. Vim is fast enough that I have never even thought about it's speed. With term, termdebug, fzf, ripgrep, and ALE with LSPs and Vim's excellent built in support for auto-completion, tag browsing, and cscope, there's really noth…

>I believe it was a mistake to fracture the ecosystem with plugins that can only be used with neovim. I hate to break this to you, but Vim itself is in the process of converting its runtime files into Vim9script (which is Vim specific), and many new Vim plugins are also being written in Vim9script. Neovim has always supported "traditional" Vimscript, and has ported all runtime file changes from Vim (think filetype pl…

I don't think the onus is on the original project to maintain compatibility with a fork. Neovim made it pretty clear from the beginning that they were going to fracture the ecosystem and now we have colorschemes in Lua that can't be used in vim... say what you will about Emacs, but at least all of their distros can run the same code.

From my perspective as a vim user, neovim has only made my life worse by splitting plugin authors into two camps without any real benefit over what we had in vim. The only good thing about neovim is it caused some nice features to be added to vim, which the neovim authors could have just contributed themselves without trying to fight for control of the ecosystem with Bram. Neovim has really just made things worse for everyone.

Re: Neovim 0.9

#72

Post by lr1970 »

henry_viii wrote: post #7
mattrighetti wrote: post #4

Earlier quoted context omitted.

Any chance your config is public? I always find cool new stuff when I look at other people’s nvim configs

You can check out these public configs: - https://github.com/NvChad/NvChad - https://github.com/LunarVim/LunarVim - https://github.com/AstroNvim/AstroNvim All of them have a Docker command where you can try them out in a container. awesome-neovim has more configs: https://github.com/rockerBOO/awesome-neovim#preconfigured-co...

Don't forget a raising star of LazyVim [0] of lazy.nvim fame

[0] https://www.lazyvim.org/

Re: Neovim 0.9

#73

Post by physPop »

vander_elst wrote: post #49

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.

The dissonance between the lua config and vimscript config is infuriating, combined with plugins not providing default config snippets (other than copy and pasting them off the their github readme's).

Re: Neovim 0.9

#74

Post by physPop »

csomar wrote: post #48
theusus wrote: post #39

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.

I don't disagree, but then you shouldn't update Neovim if you are not ready for that. I'll go even farther: don't use Neovim if you are not going to write the config yourself.

Then they'll never use neovim? That's poor advice.

Re: Neovim 0.9

#75

Post by physPop »

tarkin2 wrote: post #42

Since I've learnt vimscript and am relatively happy using it, what's the advantage of writing plugins in lua for neovim?

None that i've seen. Everyone seems to love Lua but its a mess for a config language -- its just untyped dictionaries passed around everwhere. Spelling error in some special string keyword? Too bad.

Might as well use lisp at that point.

Re: Neovim 0.9

#76

Post by physPop »

pydry wrote: post #6

For people who have used helix and neovim recently, how do they compare?

Helix takes (IMO) the very smart approach of making language server plugins "just work". The defaults are good enough for most use cases. This is a key friction point for new users of vim/neovim that don't want to spend days setting up an IDE like experience, and something vscode and helix get right.

It lacks a good config and plugin story though, so if you're not happy with the defaults its not great.

I also just dislike the different actions. Having everything be a selection just doesn't make sense to me compared to the vim style.

Re: Neovim 0.9

#77

Post by koonsolo »

theusus wrote: post #39

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.

Why not have both? https://github.com/vscode-neovim/vscode-neovim

I was using the VSCodeVim plugin, but it kept breaking. I now moved to the Neovim plugin and works great!

Re: Neovim 0.9

#78

Post by mi_lk »

ilovecaching wrote: post #71
gpanders wrote: post #69

Earlier quoted context omitted.

>I believe it was a mistake to fracture the ecosystem with plugins that can only be used with neovim. I hate to break this to you, but Vim itself is in the process of converting its runtime files into Vim9script (which is Vim specific), and many new Vim plugins are also being written in Vim9script. Neovim has always supported "traditional" Vimscript, and has ported all runtime file changes from Vim (think filetype pl…

I don't think the onus is on the original project to maintain compatibility with a fork. Neovim made it pretty clear from the beginning that they were going to fracture the ecosystem and now we have colorschemes in Lua that can't be used in vim... say what you will about Emacs, but at least all of their distros can run the same code. From my perspective as a vim user, neovim has only made my life worse by splitting p…

Probably me but I definitely sense biases in your replies.

Vim ecosystem is 'controlled' by the community not Bram. If Neovim/Lua is not good enough there wouldn't be a fracture in the first place.

The fact that Bram saw the success of Lua with Neovim but insisted on inventing Vim9Script speaks for itself. Yet you somehow manage to blame everything on Neovim.

Re: Neovim 0.9

#79

Post by pxc »

kzrdude wrote: post #18

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.

You can always find the latest Neovim in Nixpkgs Unstable, modulo a week or two. Neovim 0.9 is on its way in right now: https://github.com/NixOS/nixpkgs/pull/225152

Just make sure your user's Nix profile is included in your XDG paths like so, and the .desktop files Nix installs will get picked up by your DE: https://nixos.wiki/wiki/Nix_Cookbook#Desktop_environment_doe...

If you really want to stay on top of the bleeding edge, you can use this overlay to run prebuilt copies of Neovim nightly on any distro: https://github.com/nix-community/neovim-nightly-overlay

To ensure that the Nix installation itself is easily removable and sets everything up correctly for you, use the Determinate Nix Installer for a fast and easy installation: https://github.com/DeterminateSystems/nix-installer

In case you don't want to wait for the final package to land in Nixpkgs, command for installing 0.9 from that PR branch after using the above Nix installer is

  nix profile install github:GaetanLePage/nixpkgs/neovim#neovim
which will build from source against that PR branch.

Nix can be a great complement to a stable, conventional base system like Debian for use cases like this. I hope you give it a try!

Re: Neovim 0.9

#80

Post by pxc »

tgz wrote: post #52

I try this release on debian buster: 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?

You can probably get this version of Neovim to run on your Buster system with Nix, which will pull in a newer glibc in an isolated/self-contained way if its Neovim build needs it!

I left some instructions for how to get started with this in this comment, if you're interested: https://news.ycombinator.com/item?id=35482673

Post reply on HN