Well fucking shit motherfuckers. Vim & Neovim are both contaminated with LLM slop.

I mean, I can just use ed. Or roll back Vim to an old version and never let it update? Fuck.

I do have a new Mac coming, so I could just commit to BBEdit, tho that's less optimal for code editor. Assuming siegel hasn't done something stupid?

Ha ha I could finally switch to emacs with vile binds and then NOTHING will work.

Fucking fuck darkest fucking timeline.
https://hachyderm.io/@AndrewRadev/116175986749599825
#vim #butlerianJihad

@mdhughes
For some time I've been on the verge of writing a *toy* version of vi. Maybe I'll move that up in priority.

It also makes me think about porting Bill Joy's original vi -- but the code is difficult. It's pre-modern, so it doesn't follow niceties, and it's very very clever, because Bill Joy is a genius and he was targetting a 65 KB limit on code.

All that would make expanding its limits uncomfortable.

What about, what was it, "nvi"? I lost track of others.

@dougmerritt STeVIe and elVIs were the Atari ST/Amiga vi clones that Vim is based on, and they're both pretty hackable, ANSI C or nearly so, or were 30 years ago.

@dougmerritt @mdhughes “Heirloom” vi has been expanded for UTF-8 support and compiles easily on macOS, so I’m guessing it’ll compile easily on Linux.

https://github.com/n-t-roff/heirloom-ex-vi

GitHub - n-t-roff/heirloom-ex-vi: The Traditional Vi (vi with many enhancements from Gunnar Ritter)

The Traditional Vi (vi with many enhancements from Gunnar Ritter) - n-t-roff/heirloom-ex-vi

GitHub
@mathew @mdhughes
Interesting! Thanks for pointing out that possibility.