News for hackers. Stuff that matters.
Re:The vi family by ventana on Wednesday May 13, 2026 @12:48AM (#48117956)
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.
Re:The vi family by JohnMakin on Wednesday May 13, 2026 @02:27AM (#48118499)
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.
Re:The vi family by thunspa on Thursday May 14, 2026 @06:03AM (#48133261)
Could you share a bit more about this?
Re:The vi family by JohnMakin on Saturday May 16, 2026 @12:13PM (#48161471)
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)

Re:The vi family by raimo on Wednesday May 13, 2026 @12:50AM (#48117975)
Yes indeed, same here!
Re:The vi family by avadodin on Wednesday May 13, 2026 @04:55AM (#48119429)
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.

Re:The vi family by ab71e5 on Wednesday May 13, 2026 @08:32AM (#48121081)
Why cscope and not an LSP?
Re:The vi family by avadodin on Thursday May 14, 2026 @07:27PM (#48142571)
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.

Re:The vi family by crehn on Wednesday May 13, 2026 @09:50AM (#48121891)
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
Re:The vi family by jbaber on Thursday May 14, 2026 @10:08PM (#48143708)
Is the idea that you can stick with tmux splitting-resizing keys instead of vim ones?
Re:The vi family by crehn on Sunday May 17, 2026 @12:01AM (#48165947)
Yes!