EVi, a Hard-Fork of Vim
codeberg.org
EVi, a Hard-Fork of Vim
1–10 of 67 posts
Re: EVi, a Hard-Fork of Vim
#2I was going to comment how it might be ironic to call the project evil instead, but remembered that's the name for the vim emulation on emacs.
Re: EVi, a Hard-Fork of Vim
#3What is AI-taint and why is regular vim tainted?
Re: EVi, a Hard-Fork of Vim
#4It would be nice if specific offending portions of the codebase were highlighted. As of now, it’s hard to see why one should use this fork. Also, since the source is available, anyone can just compile a past version of vim.
Re: EVi, a Hard-Fork of Vim
#5What is AI-taint and why is regular vim tainted?
I would guess it means they accepted AI generated submissions into the vim codebase.
There's a discussion in the EVi repo about needing to find people who know vimscript. Funny enough, I am planning to use contributing some vimscript to an extension as my first AI coding agent project partly because I don't know vimscript well. Although that does mean it'll be hard to critically evaluate the output. I can compare it to the rest of the code in the extension at least to make sure it fits the style.
Re: EVi, a Hard-Fork of Vim
#6I tried to find any recent issues related to AI in the Vim repo, but did not find any.
Offending commit https://github.com/vim/vim/commit/fc00006777594f969ba8fcff67...
Just Claude as a co-author.
Re: EVi, a Hard-Fork of Vim
#7It would be nice if specific offending portions of the codebase were highlighted. As of now, it’s hard to see why one should use this fork. Also, since the source is available, anyone can just compile a past version of vim.
A cursory search didn't turn anything up in the vim repo or elsewhere. I can see why the authors of the fork wouldn't want to stir up drama, but I am really curious too.
Re: EVi, a Hard-Fork of Vim
#8> while avoiding AI taint
Don't be shy. Tell us what you really think.
Re: EVi, a Hard-Fork of Vim
#9It would be nice if specific offending portions of the codebase were highlighted. As of now, it’s hard to see why one should use this fork. Also, since the source is available, anyone can just compile a past version of vim.
Agreed. Without the context it just feels like a petty reaction. For all the reader knows, it could be completely unrelated to AI. The repository owner could’ve had a falling out with the maintainers regarding features or may be trying to inject their own malicious code into the fork.
Re: EVi, a Hard-Fork of Vim
#10What is AI-taint and why is regular vim tainted?
I would guess it means they accepted AI generated submissions into the vim codebase. There's a discussion in the EVi repo about needing to find people who know vimscript. Funny enough, I am planning to use contributing some vimscript to an extension as my first AI coding agent project partly because I don't know vimscript well. Although that does mean it'll be hard to critically evaluate the output. I can compare it…
[deleted]