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.
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
The vi family
191–198 of 198 posts
Re: The vi family
#192I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference, and development in reality is a lot of reading code and thinking about code when it comes down to it. I’ve never used it because I thought it would make me some lightning fast super developer. I’ve always used i…
I use vim because it's addictive. And that's the highest compliment I can think of when it comes to user interfaces. My fingers just love it. Every time I need to jump to a non-modal editor my muscle memory screams: "WTF?!"
How about Tiktok then
Re: The vi family
#193Earlier quoted context omitted.
> practicing this game makes you better at any number of tasks that are relevant to your daily work. Vi key bindings don't apply outside of vi
That's not true at all. Many readline and terminal based clients support vi bindings, you just have to enable them. e.g. stuff like psql. The shells themselves also support vi binding. Outside of the terminal tools like Vimium add support to browsers and many other interfaces.
Re: The vi family
#194Earlier quoted context omitted.
he did however decide to use a font which gives off comic sans vibes, which is a very interesting choice for an otherwise very barebones setup :D
openbsd has a funny cultural meme around comic sans. i've seen other writings on it but this might be the origin: https://www.openbsd.org/papers/bsdcan14-libressl/mgp00025.ht... some of the openbsd folks use it as a weapon in the fight to prioritize content over presentation. i got a chuckle out of it and it convinced me to stop thoughtlessly hating on comic sans, easy as it is.
you know what, you're right. i'm setting my terminal to this right now, haha: https://dtinth.github.io/comic-mono-font/
Re: The vi family
#195Earlier quoted context omitted.
Its probably the font that helps people with dyslexia.
hmm, not quite OpenDyslexic. looks a little like Comic Mono but maybe a little rounder? the "l" is a lot curvier than most comic-like fonts. almost reminds me of one of the annoying Samsung fonts :)
you're thinking about 'Samsung Choco Cookie' :) only know this because someone i know has this set on their phone, and looking at their screen really irritates me for some reason.
Re: The vi family
#196Earlier quoted context omitted.
openbsd has a funny cultural meme around comic sans. i've seen other writings on it but this might be the origin: https://www.openbsd.org/papers/bsdcan14-libressl/mgp00025.ht... some of the openbsd folks use it as a weapon in the fight to prioritize content over presentation. i got a chuckle out of it and it convinced me to stop thoughtlessly hating on comic sans, easy as it is.
> to stop thoughtlessly hating on comic sans you know what, you're right. i'm setting my terminal to this right now, haha: https://dtinth.github.io/comic-mono-font/
Re: The vi family
#197Earlier quoted context omitted.
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?
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
#198Earlier quoted context omitted.
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?