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

31–40 of 230 posts

Re: Neovim 0.8 Released

#31

Post by alwillis »

yoyohello13 wrote: post #15
freedomben wrote: post #8

Earlier quoted context omitted.

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…

The creator of Neovim's LSP integration is currently working on a VimL9 JIT compiler to make Vim9 plugins work for Neovim (early stages). So you still may be able to stay on the fence.

"Exciting progress on vim9script => Nvim-Lua transpiler”: https://twitter.com/Neovim/status/1575455161186664451

Re: Neovim 0.8 Released

#32

Post by freedomben »

alwillis wrote: post #25
freedomben wrote: post #8

Earlier quoted context omitted.

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...

Going somewhat off memory here, but my recollection is that was like 3 or 4 years after neovim's first release.

Re: Neovim 0.8 Released

#34

Post by alwillis »

Normille wrote: post #29
Jenk wrote: post #5

Earlier quoted context omitted.

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 conve…

The Neovim API is more fully baked now than it was.

I went through the same thing back in the day… now it’s a breeze and I’ve never coded in Lua before. Part of the problem was different users suggesting different things.

"Build your first Neovim configuration in lua” is a good introduction [1].

[1]: https://vonheikemen.github.io/devlog/tools/build-your-first-...

Re: Neovim 0.8 Released

#35

Post by alwillis »

freedomben wrote: post #32
alwillis wrote: post #25

Earlier quoted context omitted.

Vim has had :terminal since version 8.1 [1]. [1]: https://gist.github.com/mahemoff/8967b5de067cffc67cec174cb3a...

Going somewhat off memory here, but my recollection is that was like 3 or 4 years after neovim's first release.

That’s true.

Re: Neovim 0.8 Released

#36

Post by BaculumMeumEst »

alwillis wrote: post #28
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/

Treesitter is slower to parse a file initially but quicker at handling incremental changes. You probably won’t notice unless you open a huge source file.

Re: Neovim 0.8 Released

#37

Post by robenkleene »

BaculumMeumEst wrote: post #36
alwillis wrote: post #28

Earlier quoted context omitted.

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/

Treesitter is slower to parse a file initially but quicker at handling incremental changes. You probably won’t notice unless you open a huge source file.

Never used Treesitter, but I'd assume all this happens async? I.e., does Neovim actually block text editing untill the parsing is finished or do you just see unstyled content until it finishes?

(I'd just be surprised if anything new worked that way in 2022, let alone something built for async like Neovim.)

Re: Neovim 0.8 Released

#39

Post by BaculumMeumEst »

robenkleene wrote: post #37
BaculumMeumEst wrote: post #36

Earlier quoted context omitted.

Treesitter is slower to parse a file initially but quicker at handling incremental changes. You probably won’t notice unless you open a huge source file.

Never used Treesitter, but I'd assume all this happens async? I.e., does Neovim actually block text editing untill the parsing is finished or do you just see unstyled content until it finishes? (I'd just be surprised if anything new worked that way in 2022, let alone something built for async like Neovim.)

It blocks text editing until it finishes.
Post reply on HN