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

Neovim 0.12.0

github.com

Post reply on HN
Print view View original

41–50 of 271 posts

Re: Neovim 0.12.0

#41

Post by runevault »

gesis wrote: post #30
steve_adams_86 wrote: post #23

Earlier quoted context omitted.

I'm not sure how people typically use neovim, but in Zed I find multiple cursors (especially combined with multiple file buffers) extremely ergonomic for refactoring quickly and easily where tools like find and replace or simple renaming doesn't suffice. It lets you scan through and add cursors where you need them, then perform your edits across locations and even files all at once. It's so nice that it played a sign…

I am so used to sed-style, regex powered find/replace, that this use admittedly never occured to me. As a result, multi-cursor seemed mostly useless outside of pair programming that I never do. I will have to try it out once it lands in neovim just to see if I can wrap my muscle memory around it.

For me the nice thing about multiple cursors is when it would take more time to write the regex than it does to just throw down say 8 cursors and update the spots.

Re: Neovim 0.12.0

#42

Post by bluecalm »

steve_adams_86 wrote: post #23
helterskelter wrote: post #19

Up next for 0.13: multiple cursors! I have no idea what I'd do with this feature but it sounds intriguing. https://neovim.io/roadmap/

I'm not sure how people typically use neovim, but in Zed I find multiple cursors (especially combined with multiple file buffers) extremely ergonomic for refactoring quickly and easily where tools like find and replace or simple renaming doesn't suffice. It lets you scan through and add cursors where you need them, then perform your edits across locations and even files all at once. It's so nice that it played a sign…

You have very convenient macros. If there is something you want to do in places you are going to mark first then you can just execute it right there instead. If it's just one edit you just do it right there without macro and use the dot to repeat it in more places.

If those places can be created automatically then again it's just a macro you execute over many lines.

Re: Neovim 0.12.0

#43

Post by PhilipRoman »

mi_lk wrote: post #3

> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out

I always thought Vim/Nvim already had a built-in package manager, git clone inside ~/.vim/pack/*/start, am I missing anything by not using a "real" package manager?

Re: Neovim 0.12.0

#44

Post by flexagoon »

kps wrote: post #8
benrutter wrote: post #2

Always interesting when a project stays 0 ver for so long- anyone close to the project know what would be considered significant enough for a "v1" release?

Maybe when `:!` works the way vi does and POSIX says it must. Just kidding, that will never happen.

vi compatibility is explicitly a non-goal for neovim

https://neovim.io/charter/

Re: Neovim 0.12.0

#45

Post by TymekDev »

semiinfinitely wrote: post #15

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

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

Re: Neovim 0.12.0

#46

Post by lawn »

flexagoon wrote: post #38
mi_lk wrote: post #3

> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out

> how verbose it turned out Verbose? The new plugin manager's interface is literature just vim.pack.add({url}), not sure what is verbose about that

If you want to replicate the lazy features then it will get verbose. Even using a dedicated plugin for lazy loading it's not as tight as lazy.nvim.

You may argue that you don't need lazy loading, which is fine, but they're not 1-to-1 compatible.

Re: Neovim 0.12.0

#47

Post by w4rh4wk5 »

helterskelter wrote: post #19

Up next for 0.13: multiple cursors! I have no idea what I'd do with this feature but it sounds intriguing. https://neovim.io/roadmap/

Multi cursor support in VSCode replaced 98% of my need for macros. Yes, macros are more powerful, but they are pretty easy to get wrong. With multiple cursors, it's far easier to spot where your inputs don't work out and adjust accordingly.

Multi cursor is the feature that increased my productivity the most across the board.

Re: Neovim 0.12.0

#48

Post by robrain »

johnsonjo wrote: post #18
brcmthrowaway wrote: post #9

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?

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

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.

Re: Neovim 0.12.0

#50

Post by tovej »

semiinfinitely wrote: post #21

the zig build system is the only thing that actually matters in these notes. nobody maintains a parallel build system for fun—it's a clear signal they're finally pathfinding a way to migrate the core away from legacy c. zig's native interop is basically the only way to do this incrementally without the massive friction of a full rust rewrite. definitely makes nvim feel like a much more serious environment for systems…

Couldn't disagree more. Why move away from solid, mature build systems to something relatively fringe like zig.

Sadly, this is the general trend with neovim in general: less focus on stability, more and more focus on shiny new things. If I didn't have an nvim config that I'm used to I would have switched to plain vim ages ago.

Post reply on HN