Is anyone using them vim with Claude or any of these coding tools? I want to, but I haven’t found a good workflow.
I just have vim open in one terminal tab and Claude Code open in another terminal tab. Works great.
Neovim 0.12.0
111–120 of 271 posts
Re: Neovim 0.12.0
#112> - 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 always thought Vim/Nvim already had a built-in package manager
They do; I used minpac [1] back in the day with Vim. And now Neovim has vim.pack.
Every so often, a movement to create Vim and Neovim configurations with zero (or minimal) 3rd party plugins becomes popular. This means no lazyvim as the package manager.
The lazyvim package manager has all the bells and whistles, especially lazy loading plugins, which reduces Neovim's startup time if you have dozens of plugins installed. My LazyVim [2] configuration has 35 plugins total but only 6 load at startup; startup time: 76ms. Plugins you don't use often aren't loaded unless necessary.
Re: Neovim 0.12.0
#113I'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?
> Does NeoVim support Claude Code?
Why does it need to? Just open CC in another terminal window or tab. Or run it in a split inside vim, using `:term`.
Re: Neovim 0.12.0
#114I'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?
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.
> you'll be pleased to know it has plenty of its own shortcuts, as well as a "VIM navigation" mode you can turn on.
For doing something quick, VS Code's Vim mode is… fine. But not if you're something serious. I often quit it in disgust and go back to Neovim.
Re: Neovim 0.12.0
#115the 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…
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 pu…
> slowly switching to Zig
why "slow" just re-write it with ai. and to be clear im 0% joking and am prepared to be downvoted by people who haven't yet understood how feasible this kind of thing already is and how utterly trivial it will be in the near future
Re: Neovim 0.12.0
#116Earlier quoted context omitted.
The lspconfig depreciation was a very painful upgrade for me too, as it seems to be very poorly documented; but ultimately it came down to moving all of the LSP server configuration to `vim.lsp.config` blocks, then calling `vim.lsp.enable` with all the servers I use. I’m still not clear on what Mason is doing in my config after the switch but oh well.
It's documented here (with migration steps): https://github.com/neovim/nvim-lspconfig#important-%EF%B8%8F and in a pinned issue. and nvim-lspconfig :help has a migration guide: https://github.com/neovim/nvim-lspconfig/blob/16812abf0e8d81...
It's still not super intuitive with a non-trivial config and plugins. I had enough things that hooked into LSP (Mason, linting, inlay hints, etc.) that I needed to spend a couple of weekend afternoons moving my configs over. For a lot of my config it was an all or nothing migration.
Re: Neovim 0.12.0
#117the 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.
I've found Neovim to be remarkably stable, even when building from main.
Re: Neovim 0.12.0
#118I'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?
If it's because VSCode has built in IDE features like LSP integration, I personally really like Helix. Keyboard based (although not the same movements as Vim/Nvim, it didn't take me long to switch), and it's got built in LSP integration/stuff just works out of the box.
Although no LLM support in the editor, I personally just run Claude Code in a separate terminal, but if you want AI in the editor you'll have to look elsewhere.
I did try Neovim with Copilot a while back, and Google shows a few NeoVim Claude Code plugins, so it's probable that if you want an LLM in your text editor, NeoVim might work :)
Re: Neovim 0.12.0
#119My #1 issue with Neovim is the new ! Behavior. Anyone know how to make it toggle the alt terminal screen and just output to the primary screen like it does in Vim?
the thread here may be useful: https://news.ycombinator.com/item?id=47565813
Re: Neovim 0.12.0
#120My #1 issue with Neovim is the new ! Behavior. Anyone know how to make it toggle the alt terminal screen and just output to the primary screen like it does in Vim?
What are you doing with ! that requires this? Some alternatives I can think of depending on the use case are ^Z or :term.