Hacker News new | ask | show | jobs
by ventana 39 days ago
One thing I noticed that with Claude Code and Codex running in the terminal, I tend to use VS Code much less than before, and found myself opening files in vim more often. It just looks like, for me, the agent development brings me back to using the basic tools, like many years ago, before VS Code existed.
4 comments

This is interesting to me. vim was my main editor since the start of my career and I was very fast with it, much faster than my peers with an editor. at the outset of llm’s, I ended up using a plugin that would utilize bindings to help me edit faster. with claude code, and how fast it is making changes across many files, I almost never use vim anymore, or vi, unless I need to inspect files in a container/server.
Could you share a bit more about this?
there were plugins where I could quickly describe the edits I wanted, and it would utilize my existing bindings and shortcuts to do stuff that was very common for me. It was more of a fun trick than useful, I guess, but it saved keystrokes, and I have severe tendonitis, so it was nice.

Nowadays almost never enter vim, because it is 100x faster than I could ever be. I use it for viewing files occasionally but reviewing edits in the claude or codex window usually works just as well. It’s the first skill I expect to decay for me (vim)

Funny, because the only reason I fire up VSCode is to chat up the bots because we are AI-compliant now and the customers pay for it.

I tried nvim integration but it was half-baked and I can't even use nvim as an editor because they removed cscope support. nvi back in the day also dropped support for cscope because it wasn't vi enough. Hell, there is barely a working source repository for it. Only vim supports it out of the box. Am I the only person using cscope in 2026?

As of current day, I only use vim with no plugins to edit source code.

Why cscope and not an LSP?
Because I've been using it for over 30 years?

I knew there were more visual studio type plugins that may also fit my needs but as I said I do not use plugins. If I install "vim" and it isn't in it, I most likely am not going to use it.

A "language server" also sounds all kinds of wrong although I suppose the function is the same.

Same. And if I may, that led me to creating a Vim file browser that runs in a separate terminal (tmux pane!) so I have fewer window navigation shortcuts to remember: https://github.com/hoffa/vitree
Is the idea that you can stick with tmux splitting-resizing keys instead of vim ones?
Yes!
Yes indeed, same here!