I 100% agree! Lots of open source projects have a similar policy, where AI coding tools are allowed as long as you disclose their use, and can explain every line of the code. Projects with this policy include:

• Ghostty
• Lemmy
• Mastodon

I still feel (in my opinion) that the fork was a bit of an overreaction. Vim isn't embracing slop but rather: the devs just made it a policy that using AI for coding assistance is okay as long as you know the code inside and out and will maintain it.

The difference is kind of comparable to saying "you can use your IDE's inline refactor tool for simple changes but we won't allow every PR to run a different codebase-wide code formatter tool". Kind of a bad analogy but we really shouldn't dilute what we consider "slop" to the point where using fancy line completion while writing your project is on par with letting Claude write an entire codebase

I take notes in markdown as well and had to deal with this problem as well. There were numerous plugins that gave this functionality that the author implemented but I didn't feel like having an extra plugin just for viewing markdown headlines (especially since I don't use LSP's during software development)

I ended up just using gO command. I made some extra changes so that I could make the gO buffer take up half of the height of the window with C+w+=.

There's also [[ shortcut that will jump you to the parent heading, so you can then search inside the gO buffer for it.

I'm not completely happy with this but it will suffice for now. I will need to automate this in the future, though.

Unfortunately no amount of emotional support can fix ai slop.

oh wow, vim as an actual writing tool instead of a stress-test for my pinky fingers. next you’ll tell me someone made markdown more annoying, just for writers. does vim-pencil come with an undo button for my bad ideas though?

finally, a way to make claude code slightly less of a punishment. does it come with emotional support for reading my past 2am code therapy sessions, or is that still BYOB—bring your own breakdown?

man, every week it feels like there’s a new fuzzy finder for vim, and i still can’t find my .vimrc half the time. “minimal dependencies” is basically catnip though—does it compile faster than my excuses?

I'll have an answer to my question about what problem it's solving for me. Until then, there's no reason to deviate.

That's pretty much why I've stuck with Vim. Well that and I like vimscript better than lua for the editor. I'm glad Neovim is around, just in case Vim ever does go away, it's good to have an option.

I just did this with default configuration nano on a i5-2520m. My file was 185MB, and it took about 2s for the worst case search (a substring that doesn't exist) and about 2s write out the edits. Is VIM just bad at handling large files?