Discussion

Search code, repositories, users, issues, pull requests...

benrutter: 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?

brcmthrowaway: 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?

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

c-hendricks: I unintentionally ran the main branch when testing some changes and a lot of my config broke (mostly around LSPs, CodeCompanion was much slower streaming its responses) so might wait a bit before upgrading.

mi_lk: > - d21b8c949ad7 pack: add built-in plugin manager `vim.packCan 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

c-hendricks: I'm assuming there will be something like lazy.nvim built on top of vim.pack. Some of the conventions might go away (ie constantly calling `.setup`).

suby: There is a roadmap and github issue tracking what is needed for 1.0.https://github.com/neovim/neovim/issues/20451https://neovim.io/roadmap/

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

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

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

pawelgrzybek: Have a look here. This is incredible guide to the `vim.pack`.https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack....

wasabi991011: 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: What do you use?

semiinfinitely: 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-level performance work.

helterskelter: 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/

johnsonjo: 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

markrian: What are referring to, out of interest? Does this apply just to nvim, or vim as well?

pl-94: 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!

tekawade: You can use vim key binding in vs code.

steve_adams_86: 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 significant role in me keeping Zed early on despite it missing a lot of extensions I used in VS Code.

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

tekawade: Lookup helix tutorial. It’s pretty useful.

toisanji: Is anyone using them vim with Claude or any of these coding tools? I want to, but I haven’t found a good workflow.

tekawade: Tried to switch but found lazy.nvim better

meekins: Really excited about this! At least in Sublime Text I've found multiple cursors a really powerful tool for ad-hoc transformations on snippets of semi-structured text or instantly and visually applying the same edit on multiple similar lines.

NegativeLatency: It being built in sounds nice, although I have some lines in my config that automatically install lazy if it’s missing.

scuff3d: It's funny because I miss this one all the time. I got use it in Sublime and VScode before making the jump to Neovim. I know you can get similar functionality from macros and what not, but it's just not the same.

flexagoon: vi compatibility is explicitly a non-goal for neovimhttps://neovim.io/charter/

PhilipRoman: 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?

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

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

jauntywundrkind: 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/34009Last, 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.

djb-at-durable: Just nvim. Neovim runs :! commands non-interactively, capturing the output in a pipe. vim, on the other hand, suspends itself and runs the command in an external shell.This isn't a problem, really, for non interactive commands, but causes issues with interactive ones. I personally prefer vim's approach, though not enough to abandon neovim.

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

aldanor: 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

mihaelm: It doesn't necessarily mean they're going to migrate from C, building a C project is just so much nicer with Zig than fiddling around with CMake. You got people using it as a build system even for Go projects, especially if they're relying on CGo.However, if you were entertaining the idea of slowly switching to Zig, the build system would be the place to start. Moving away from CMake is worth it even if you don't push it further.But yeah, the C-Zig interop story is so good it's a no brainer if you want to "modernize" your C codebase, and you can do so incrementally instead of stopping the world for a rewrite.

PhilipRoman: In Vim, :! cleans up the tty context and hands it off to the child program, to do whatever it wants, you can open any TUI program and it will work as expected. In Neovim, :! just uses a plain pipe. Actually I believe GVim has the same problem. Since both Vim implementations now have a built in terminal handling stack anyway, I wonder if that could be used to unify the behavior.

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

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

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

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

wilkystyle: 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

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

saint_yossarian: [delayed]

eviks: 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

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

imjonse: It probably goes against Vim tradition, culture and freedom to choose, but I wish they added even more built-in features (like Helix) that are currently implemented in competing and sometimes brittle plugins and have to be put together into also competing vim starter packs and distros of plugins and config files just to have a modern setup out of the box.

OliverWich: Sidekick.nvim is nice, you get a "real" terminal window on the side with many different agents to choose from.Either opencode, claude, gemini, copilot, basically most that are relevant :DIts a pretty light connection-layer, so it helps with sending context.

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

skydhash: Define “modern”!Almost all such complaints are close to “I want to be cool and be seen as an haxor, but all I know is a bit of VSCode and IDEA, make it easier for me, plz”.

andrepd: Multiple cursors were the killer feature that got me to start using Sublime Text back in ~2010. Still an absolute staple of my text editing toolbox. Ctrl-D Ctrl-D Ctrl-D ...