Live data from Hacker News

Neovim 0.12.0

github.com

51–60 of 271 posts

Re: Neovim 0.12.0

#51
post #30

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.

I've always told myself I should learn to do these sed/regex find and replace techniques, but my origins are not sophisticated and I use computers like that orangutan hammering nails in the video with David Attenborough https://youtu.be/IFACrIx5SZ0?si=NcWGBNq272KoYB2i&t=84

It's entirely possible that you don't need multiple cursors

Re: Neovim 0.12.0

#52

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…

> the only way to do this incrementally without the massive friction of a full rust rewrite

Any rewrite is massive friction, I’m sure probably meant port? The only annoyance with Rust ports is if you have to support varargs. Hopefully that will come to an end soon.

Re: Neovim 0.12.0

#53
Congrats on diff mode improvements. Hopefully forge style highlighting mode for two way diffs will be available next.

Re: Neovim 0.12.0

#54

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/

You'd do text editing with it with the coolest feedback loop - immediately seeing the changes and what those changes apply to beforehand, that's different from having to repeat some macro multiple times

Re: Neovim 0.12.0

#56

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

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 as a built-in.

Re: Neovim 0.12.0

#57

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/

Whats with all the fuss over multicursor. How is this different from just using '.'

dot repeat is the wrong comparison. A closer one would be macros, but even then a good multiple cursors implementation is often faster, more intuitive, and requires less cognitive overhead. One of the better examples of the usefulness of multiple cursors is from Emacs Rocks (link goes to 0:23):

https://m.youtube.com/watch?v=jNa3axo40qM&t=23s

Re: Neovim 0.12.0

#58

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?

[dead]

Re: Neovim 0.12.0

#60
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?

I imagine you are left with manual dependencies, manual updates, and possibly without lazy loading or portable configuration. That stuff is not strictly necessary and may be easy to roll your own if you're very into it, but it's comfortable to have a standard.
Post reply on HN