2026-09-13 16:06 UTC
@meanmicio@todon.eu @jaypatelani@bsd.network I looked at it, it seems both projects have the same goal (provide a pre-AI vim)
vim-classic set the cutoff explicitly at 8.2, explicitly not allowing Vim9 script, as it was not complete when vim started taking on slop. It’ll thus be a maintenance project for vim 8.2 and no new features being developed.
I wasn’t able to find what strategy Evi uses, they fork at a much later time, vim 9.1, just before the first AI commit. But will they add features? Will they stay compatible with vim? Will they backport features by rewriting them without AI?
Replies (1)
-
@meanmicio@todon.eu 2026-09-13 16:17
@jornane@mastodon.bsd.cafe @jaypatelani@bsd.network Many good questions! :) I adopted EVi mainly because I still can use vi functionality without the slop. I am positive vim-classic will work just fine, too. BTW, just read Drew's blog post about why vim-classic. It is beautiful (https://drewdevault.com/blog/Forking-vim/) ❤️ 🤗