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

Neovim 0.8 Released

github.com

Post reply on HN
Print view View original

21–30 of 230 posts

Re: Neovim 0.8 Released

#21

Post by Cupprum »

dyingkneepad wrote: post #4

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

I switched to neovim because of LSP (Language server protocol) support. I know there are libraries (or whatever cool kids call it these days), which brings this functionality to og vim, but the lsp integration in neovim just works so nicely out of the box.

Re: Neovim 0.8 Released

#23

Post by BaculumMeumEst »

I really wish neovim could ship usable default colorscheme and round out its lsp support with autocompletion. Treesitter isn’t for me; it’s slower to open files and I have no idea how people make sense of so many different color groups.

Still sticking with vanilla vim and CoC for the time being, they’re rock solid.

Re: Neovim 0.8 Released

#24

Post by [deleted] »

BaculumMeumEst wrote: post #23

I really wish neovim could ship usable default colorscheme and round out its lsp support with autocompletion. Treesitter isn’t for me; it’s slower to open files and I have no idea how people make sense of so many different color groups. Still sticking with vanilla vim and CoC for the time being, they’re rock solid.

[deleted]

Re: Neovim 0.8 Released

#25

Post by alwillis »

freedomben wrote: post #8
dyingkneepad wrote: post #4

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

Yeah it's a tough one. I've switched back and forth relatively freely over the years, but now that new VimScript (vim9 script) has breaking changes and neovim will not be supporting it, it's probably time to pick a pony. I may end up sticking with og vim but my heart has always been with neovim. regular vim would undoubtedly still be stuck in the stone age (including with no :terminal) had neovim not started some com…

Vim has had :terminal since version 8.1 [1].

[1]: https://gist.github.com/mahemoff/8967b5de067cffc67cec174cb3a...

Re: Neovim 0.8 Released

#26

Post by kuratkull »

coinbasetwwa wrote: post #11

I still haven’t recovered from the last couple updates… I’ll probably be making the switch to VIM very soon.

You make it seem like some obvious things were recently broken/changed. I have used NeoVim for a couple of years, I haven't noticed any breaking changes. Please elaborate

Re: Neovim 0.8 Released

#28

Post by alwillis »

BaculumMeumEst wrote: post #23

I really wish neovim could ship usable default colorscheme and round out its lsp support with autocompletion. Treesitter isn’t for me; it’s slower to open files and I have no idea how people make sense of so many different color groups. Still sticking with vanilla vim and CoC for the time being, they’re rock solid.

Treesitter isn’t for me; it’s slower to open files

I certainly haven’t experienced any slowness with opening files with Neovim with Treesitter. It certainly enables much better syntax highlighting, among other things [1]. If anything, it’s faster than the regex-based syntax highlighting that Vim traditionally used.

CoC is a 3rd party LSP plugin that works with Vim and Neovim.

[1]: https://neovim.io/doc/treesitter/

Re: Neovim 0.8 Released

#29

Post by Normille »

Jenk wrote: post #5
dyingkneepad wrote: post #4

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

Neovim is vim 8 compatible. It _also_ supports LUA script for config and plugins, has native LSP support, and runs much more efficiently. You can run your current .vimrc using neovim.

  >Neovim ... supports LUA script for config and plugins
Except it doesn't really. Or at least it's very basic. I'll re-post a comment I made on this, when it was discussed a while back [0]

https://news.ycombinator.com/item?id=32624308

----

I've been using Neovim for several years now. Not for any real reason, other than "Let's try 'new & shiny'" when it first emerged. Last week I thought I'd finally get round to converting my existing Neovim init.vim config [which had itself been inherited and developed from my earlier Vim .vimrc one] to Lua [not a language I'd ever used before. But the syntax looked fairly straightforward].

What a waste of time! The easy stuff [enabling/disabling various options] was easy. But then it's easy in Vimscript too. The difficult stuff [defining autocmds, managing my plugins] was either completely ignored in every single "convert your init.vim to to init.lua" tutorial I read... or required wrapping the existing Vimscript block in

  vim.cmd[[ ... ]]
in Lua because Neovim's Lua support can't yet do a lot of this stuff natively. Oh, and this also had the brilliant side-effect of removing syntax highlighting from great swathes of my config file as everything inside vim.cmd[[ ... ]] is rendered as a comment. I spent the best part of a day wrestling with converting to init.lua, left it overnight and then, in the morning thought Why the fuck am I wasting time trying to beat this into shape, when my existing vim.init is already set up exactly how I want it?" and I reverted back to good ol' crusty ol' unfashionable Vimscript.

YMMV if you're actively developing plugins and want to use a more widely utilised language to write them in. But for configuring Neovim itself, Lua is more hassle than it's worth.

Post reply on HN