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

81–90 of 106 posts

Re: Neovim 0.9

#81

Post by throwawaysalome »

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…

the more Vim transitions to Vim9script, the less ... "fracturing of the ecosystem" [can be attributed to] Neovim.

I see what you did there.

Re: Neovim 0.9

#82

Post by michaelanckaert »

physPop wrote: post #74
csomar wrote: post #48

Earlier quoted context omitted.

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.

Vim/neovim/emacs are all tools for power users, writing your own configuration and extensions is intended. The authors of these tools have no wish to capture market share or users. Use vscode if it fits you, no one minds or cares.

Re: Neovim 0.9

#83

Post by gorjusborg »

wadd1e wrote: post #2

Congrats to the Neovim team! I know one complaint that people tend to have with nvim is that they can never get to a stable config that they don't need to keep tweaking; I used to be one of those users that kept making changes to their config but I've had a stable config for roughly 6 or so months now and I've been loving neovim and the fact that it's personalised exactly to my liking. So what I'm trying to say is th…

Custom config is not necessary to leverage vim or neovim effectively.

This is a personal usage issue. The fact that you can customize it doesn't mean one needs to, or should.

I run with a mostly vanilla config and a few plugins and have not had to change config for years.

Re: Neovim 0.9

#84

Post by theusus »

worksonmine wrote: post #55
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'd suggest learning and understanding the vim way of doing things instead of trying to shoehorn the workflow you're used to from VSCode. It's a different world, and it can be really fun to explore but you have to commit. 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'. T…

I don't think the cost versus return ratio is that good for that. I better churn Leetcode questions and get better job

Re: Neovim 0.9

#85

Post by gpanders »

vander_elst wrote: post #54
quesera wrote: post #14

Earlier quoted context omitted.

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…

> Everything works just like it's supposed to 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.…

>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

Maybe I'm misunderstanding, but the Nvim terminal does not do this, at least by default (maybe some plugin enables this "feature"). If you yank some text from a terminal buffer in Nvim and paste it into another buffer with p, no line numbers are added.

Re: Neovim 0.9

#86

Post by gpanders »

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.

>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

Could you elaborate on this? Out of the box, Neovim and Vim are extremely similar, almost identical to a first approximation (Neovim has different defaults for some options than Vim, but that's about it). The two start to diverge dramatically when you begin writing or using plugins as the extensibility/API model is quite different between the two, but I am very surprised to hear you had difficulty trying to make Neovim behave like Vim.

Re: Neovim 0.9

#87

Post by weakfish »

AlexSW wrote: post #41
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

OP didn't reply, but here's my set of dot-files in case you still wanted to have a gander at someone's. You can find the Neovim configuration in the neovim directory. https://github.com/AlexSWall/dot-files

And here is mine - it’s goal is parity with VS Code, but in a single file that’s well organized (based on kickstart.nvim)

https://github.com/weakphish/dotfiles/blob/master/.config/nv...

Re: Neovim 0.9

#88

Post by earthling8118 »

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…

No, that's just not how it works. The original project came back to fracture the ecosystem in response to the fork that did not do so.

Re: Neovim 0.9

#89

Post by earthling8118 »

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.

I'm not a fan of installs that aren't reversible either. That's why I don't touch any distro that fights me on that (such as one that supports .deb)

Re: Neovim 0.9

#90

Post by jgb1984 »

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.

A shame they removed the .deb package. Oh well, I use gvim as my daily driver anyway.
Post reply on HN