upvote
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
reply
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.
reply
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.

reply
Why cscope and not an LSP?
reply
Yes indeed, same here!
reply