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.
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
c-hendricks 5 minutes ago [-]
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`).
benrutter 13 minutes ago [-]
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?
suby 7 minutes ago [-]
There is a roadmap and github issue tracking what is needed for 1.0.
Maybe when `:!` works the way vi does and POSIX says it must.
Just kidding, that will never happen.
brcmthrowaway 2 minutes 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?
Rendered at 18:36:07 GMT+0000 (Coordinated Universal Time) with Vercel.
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
https://github.com/neovim/neovim/issues/20451
https://neovim.io/roadmap/
Just kidding, that will never happen.
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?