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

Neovim 0.7 Released

github.com

Post reply on HN
Print view View original

101–110 of 220 posts

Re: Neovim 0.7 Released

#101

Post by canaus »

ducktective wrote: post #35

People who have tried both vim and nvim: - I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment? - Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sit…

I came from coc.nvim and switched to the native LSP when it was released on nightly. For a while I was using VSCode and came back to nvim and switched back to coc.nvim.

I found that the native LSP's community to be too quickly changing. Plugins that were necessary earlier weren't, while new necessary plugins came into play. But, coc.nvim was steady chugging along and my old settings file worked out of the box.

I'm also not a huge fan of just the sheer amount of plugins that use the LSP. It seems like every plugin has go-to functionality.

Re: Neovim 0.7 Released

#102

Post by lawn »

pdimitar wrote: post #41
ilovecaching wrote: post #17

Earlier quoted context omitted.

It's a weekend of learning for a tool that you use your entire life. Any computer scientist should realize the power of amortization.

I absolutely want to learn VIM but saying it's only a weekend is plain misinformation. We're definitely looking at months of gradually building new habits.

I think the difference between your and the other opinion is what does "learn vim" mean?

Is it enough to know how to enter insert mode, make an edit, then save and quit? That's easy enough to learn in a weekend.

Or is it learn how to edit efficiently using the various vim commands? That will indeed take much longer than a weekend.

(Even getting it configured just the way you want to will probably take more than a weekend...)

Re: Neovim 0.7 Released

#103

Post by lc9er »

DavidWoof wrote: post #48
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

I could ask the opposite: why do people choose terminal vim when you can easily add nvim integration to editors like VSCode and get 98-100% of what vim gives you along with much easier configuration of all those extras you mention like autocomplete, hover reference, refactor, etc.? That's a bit of an overstatement, because I really do love vim/nvim and nvim integration isn't that good, but the fact is that adding a f…

I used this combo for a while, but there was a period of time where VSCode updates would break the vim integration. This was a few years ago, and I’ve recently reinstalled VSCode for use with F#, since Ionide seems to work better than in Neovim.

Re: Neovim 0.7 Released

#104

Post by CameronNemo »

elpatoisthebest wrote: post #84
ducktective wrote: post #35

People who have tried both vim and nvim: - I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment? - Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sit…

I do recommend that new users just use coc.nvim, but not exactly because of what you said. Both coc.nvim and the built in LSP implementation use basically the same Language Servers, so whatever updates happen to the server will benefit either approach. However, coc.nvim DOES have a large community that has built a neatly packaged LSP client framework (and many other tie-ins like completion, snippets, formatting, and…

If you have ever said the word "bloat" unironically on your computer with 64G of RAM, built in might be for you.

I really just want one config that works on:

* Yes, my Ryzen 5 with 32G of RAM

* My Pinebook Pro with 4G of RAM (and like 3.7G accessible) (and limited storage as well)

* My jump host / gateway VM with 512MB of RAM (and even more limited storage than the PBP)

So pulling down and running node.js to use coc.nvim has never been something I was interested in. Before nvim-lspconfig I used LanguageClient-neovim (a Rust client).

Re: Neovim 0.7 Released

#105

Post by lambdaba »

xboxnolifes wrote: post #100
lawn wrote: post #77

Earlier quoted context omitted.

If you're a lifelong programmer the time it'll take to be proficient in Vim is a drop in the bucket in the grand scheme of things. A tool that can last a lifetime and be used for any programming language at that. It's just a trade-off between optimizing for the short-term or the long-term.

> If you're a lifelong programmer the time it'll take to be proficient in Vim is a drop in the bucket in the grand scheme of thing I just don't see it? I spent a good 6 months only using vim to see if I could get it to stick. Then I took a year break. After the break I forgot nearly every shortcut I was using minus a select few. I never got to the point of even matching my efficiency in other editors, let alone surpa…

I spend most of my time inside a terminal and have my shell configured so line editing is as much like Vim as possible. Also configured Vim modes everywhere else possible.

Also, although historically that hasn't really been part of the Vim ethos (compared to Emacs at least), you're expected to mold your editor over time to suit your needs exactly.

Re: Neovim 0.7 Released

#106

Post by wussboy »

davidkunz wrote: post #82
annowiki wrote: post #55

Earlier quoted context omitted.

The debugger. I made your same argument for years to a buddy of mine that always used WebStorm (I'm a Python dev and he kept pushing me to try PyCharm). A coworker pushed me to try PyCharm since we're on Windows and I haven't really looked back. I even bought CLion. If you can point me to an easy debugger to set up in neovim I'd probably be right back, but I can't. Couldn't figure out how to set up vimspector. And in…

Debugging in Neovim is quite simple, I recommend nvim-dap, I made a few videos: https://youtu.be/ga3Cas7vNCk https://youtu.be/SIYt1dopfTc If you prefer Vimspector: https://youtu.be/-AZUIL1rY3U

I watched your first video. As someone who likes the idea of Vim and has learned many of the keyboard shortcuts, my impression of the video was "Debugging in Neovim is quite simple. Just remember these 35 keyboard shortcuts."

Re: Neovim 0.7 Released

#107

Post by gpanders »

nerdponx wrote: post #94
gpanders wrote: post #24

I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/

This is really helpful, thank you! Does the new filetype.lua script still run the ftdetect/ scripts? Or will those only be run by the filetype.vim fallback and need to be ported to the new system?

Yes it does.

Re: Neovim 0.7 Released

#108

Post by canaus »

andrewmcwatters wrote: post #99

Neovim is such a weird derivative utility to me. Derivative/forked software usually isn't very successful to begin with, but then Neovim makes attempts to be modern and it's so not appealing at all. Here are some 5 second examples. Example 1: nvim . Still uses Netrw, which is fine, but doesn't even attempt to do things like: let g:netrw_preview=1 let g:netrw_banner=0 let g:netrw_browse_split=4 let g:netrw_liststyle=…

I'm confused on the arguments presented. Is it that the out-of-box functionality isn't as good as other GUI based editors, or that certain things are off by default?

I agree that certain settings shipped with neovim could be expanded. There should really be a process to elect plugins and settings that are generally accepted as "good" for neovim.

Plugins like Gruvbox, vim-surround, coc.nvim, vim-plug, nerdtree etc. have been continuously maintained for years, why not make it easy for new users to install and use them without having to go on the path of wonder?

Re: Neovim 0.7 Released

#109

Post by CameronNemo »

ducktective wrote: post #35

People who have tried both vim and nvim: - I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment? - Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sit…

you may be interested to know: https://news.ycombinator.com/item?id=31041616

Re: Neovim 0.7 Released

#110

Post by qbasic_forever »

lua is such a nice and sane language for application config. I really enjoy neovim's choice to use it, and with this release more or less allow 100% of typical configuration to be done entirely in lua. Good riddance to bespoke scripting languages.
Post reply on HN