Neovim 0.12.0 - Hacker News

Posted by pawelgrzybek 3 hours ago

130 points | 60 commentspage 2

jauntywundrkind 2 hours ago|

I've been loving NeoVim with AstroNvim so much. I'd done some editor configuration and it felt daunting and mostly just... didn't. And I was not good about using the leader key, because of tmux to zellij problems, that nothing was discoverable (zellij adds visual overlays to guide you through usage, unlike tmux's memorize everything approach). AstroNvim has changed both of these so much for me: there's excellent community packs (https://github.com/AstroNvim/astrocommunity) that are easy to drop in that have good configuration out of the box for everything you could want to do, and the leader key has a wonderful little bottom-of-screen UI for itself that helps you discover what's available (that astronvim plugins naturally grow/augment).

On Neovim, very exciting and interesting to see 0.12.0. It'll be interesting to see if folks really do migrating and at what speed to the new built-in plugin system. There's still dozens of other still used plugin systems, but LazyVim seems to have really cemented itself as the lead (and is used in AstroNvim). It feels like vim-pack is trying to be lighter still. Will it work? Will it get adopted? Will be neat to see. PR for vim-pack: https://github.com/neovim/neovim/pull/34009

Last, I still dream of a day where neovim headless is capable of running multiple different clients at once. The rpc architecture is so powerful and so amazing. But we're still (afaik) anchored to having once canonical screen, where-as I want to be able to have multiple editors, looking at different views of the workspace, with different layouts, and specialty windows like IDE debuggers in their own layouts. It's hard to dream of neovim disaggregating itself, blowing up the screen.c, but maybe maybe maybe maybe some decade, possibly, I hope.

brcmthrowaway 2 hours ago||

I'm using VIM - Vi IMproved 9.1. What am I missing?

I'm kind of desperate to switch. Getting massive FOMO from colleagues using VS Code. But I really like using the keyboard to navigate. What should I do?

Does NeoVim support Claude Code?

johnsonjo 2 hours ago||

I've been using VIM/NVIM on and off for a while and the one thing that made it stick for me over VSCode was LazyVim [1]. If you're missing out on something IDE like VSCode, but you love vim it's a great way to go (it can take some getting used to so hang in there). EDIT LazyVim is based off nvim by the way. If your more into videos to learn about something this is a good intro to it from Elijah Manor [2]. I have my dotfiles stored on github that I use on my different machines, and use gnu `stow` and `make` to build them and that gives me my specific lazyvim setup free and quickly after just downloading a few dependencies.

[1]: https://www.lazyvim.org/ [2]: https://youtu.be/N93cTbtLCIM

robrain 1 hour ago||

To pile on to the LazyVim love, I recommend this site: https://lazyvim-ambitious-devs.phillips.codes/

Course and book (free html, available pdf and dead tree). Covers everything I've needed concisely.

lachlan_gray 1 hour ago|||

Ymmv, but I have been very happy using classic vim’s “native claude support”

:term claude

It will also expand special characters so you can do something like

:term claude “refactor %”

And Claude starts work on your current file right away. Also your buffers will update with Claude’s edits!

aldanor 2 hours ago|||

Most of the active development in the ecosystem is done for neovim these days. If you're using barebones vim then yea you probably won't see much difference, otherwise you have no choice

wasabi991011 2 hours ago|||

If it's just using the keyboard that's holding you back from VSCode, you'll be pleased to know it has plenty of its own shortcuts, as well as a "VIM navigation" mode you can turn on.

brcmthrowaway 2 hours ago||

What do you use?

sequin 2 hours ago|||

Resist hypes and just use whatever you feel like. Torvalds uses a 40 year old EMACS implementation and that seems to be working for him.

NegativeLatency 2 hours ago|||

Used neovim and neovide for the last week (also had FOMO) and while they’re good (no major gripes) I ended up going back to macvim.

Are there specific features you’re missing from vscode?

pl-94 2 hours ago|||

I motivated my Cursor-colleagues to switch to tmux+nvim -- they don't use it all the time, but they enjoy the vibe. Claude is running on some tmux pans. Much nicer than VSCode!

normie3000 2 hours ago|||

What's the FOMO caused by? Asking as a vim user starting to get FOMOOFOMO.

tekawade 2 hours ago|||

You can use vim key binding in vs code.

scuff3d 2 hours ago|||

Use the Neovim extension for VScode. It requires you to have Neovim installed, but it works way better then the Vim extension since it passes commands to neovim instead of using emulation.

lawn 2 hours ago|||

What are you getting FOMO over? Been using Neovim since it forked from Vim and I'm very happy with it.

Lua has been a big boon to advanced configuration and the plugin ecosystem and Neovim supports everything I'd want and more. LSP and treesitter for instance are still better handled by Neovim.

If you dislike Lua (I'm not a fan) I recommend Fennel, but either way it's much better than Vimscript.

As for Claude there are at least two Neovim plugins for it. I use one of them and it works well but I can't remember which.

braben 1 hour ago||

[dead]

semiinfinitely 2 hours ago|

why put a built-in plugin manager. and if so why make it pack not lazy

TymekDev 1 hour ago|

> The folke/lazy.nvim is the most used plugin manager at the time of this writing. And rightly so: it is very capable with lots of features. Ironically, this itself makes it not very suitable to be a part of Neovim as most of the features come with significant code and maintenance complexity. Plus the whole idea of treating lazy loading as the main goal of a plugin manager does not sit well with Neovim core team.

https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack....

shmerl 1 hour ago||

I'd stick to lazy.nvim for now. Lazy loading is really neat and lazy.nvim's ability to specify plugin dependencies isn't something vim.pack has either.

I'd guess if you don't care about lazy loading and OK with just loading everything all the time - vim.pack is great to have.