Post #4455755

2026-08-07 14:34 UTC

@synlogic4242@social.vivaldi.net @rl_dane IMHO, vim has added little of value for me to vi. I still use the same 10 vi commands that I first learned. But now vim does stupid, like allowing me to open and edit directories. Every time that happens, I'm all wtf wtf wtf get me outta here!?! The context coloring is nice, though, so I magnanimously allow others to use it.

Replies (2)

@synlogic4242@social.vivaldi.net 2026-08-07 18:08

@skewray@mathstodon.xyz @rl_dane I cannot disagree on vim vs vi. I have a TODO to pin my vim versions because the new post-Moolenaar maintainer has started allowing AI commits. but have punted on the hassle. vi is the only FOSS tool I've seriously considered maintaining my own fork, but I'm reluctant to take on any extra LOE to my plate. too many things I should be doing or want to be doing as it is, dagnabbit. (unless I could brand it as "vi.ai" with a hard promise of NoAI used, allowed or supported, and still land some of those sweet sweet AI VC gazillions)

Open ##4455754
@rl_dane@snac.bsd.cafe 2026-08-09 01:35

@skewray@mathstodon.xyz @synlogic4242@social.vivaldi.net I spent some time learning ed in May, which of course made my understanding and use of sed explode. But it also gave me an appreciation for vanilla vi (nvi). Its feature set is really quite impressive, considering how old it is (a 1994 re-write of a 1976 editor). I need to try compiling "heirloom vi" some time, although I must admit I'm spoiled by nvi2's Unicode capability.

Open ##4455824