EDIT: I updated the fork to last commit before the AI slop.

[mrmasterkeyboard@mastodon.social]

@thing @lu_leipzig How about Vimprovisation?

[lu_leipzig@troet.cafe]

@mrmasterkeyboard @thing Anything with "vim" in the name is asking for trouble, trademark-wise.

[mrmasterkeyboard@mastodon.social]

@lu_leipzig @thing didn't think it was trademarked, but I guess we'll go with EVi then. Excellent Vi.

[thing@plasmatrap.com]

@mrmasterkeyboard@mastodon.social @lu_leipzig@troet.cafe not just excellent vi, it can stand for much more :)
eepy vi ​​
extraordinary vi ​​
expanded vi ​​
eVi (as in gentoo) ​​
emby vi ​​
...
i think we should leave it up to the user :)
so just EVi.

[mrmasterkeyboard@mastodon.social]

@lu_leipzig @thing (another reason why i picked EVi, it sounds like VMware's ESXi.)

[mrmasterkeyboard@mastodon.social]

@thing @lu_leipzig Easy Vi, Extended Vi, Electric Vi, Elected Vi, Eradicated Vi, Everybody (yeeeaaaah!) Vi, Every Vi

[thing@plasmatrap.com]

@mrmasterkeyboard@mastodon.social @lu_leipzig@troet.cafe yeah, like that :)

[mrmasterkeyboard@mastodon.social]

@thing @lu_leipzig https://codeberg.org/NerdNextDoor/evi/issues/1#issuecomment-11386354

[kaleissin@wandering.shop]

@mrmasterkeyboard I would like to have a vim that is Bram's vim, maintained forever. Feature freeze.

[mrmasterkeyboard@mastodon.social]

The first commit by me to the EVi editor, a fork of VIm before the AI slop.

https://codeberg.org/NerdNextDoor/evi/commit/99d7fe946837131607e0b1cacbb3fb9a63cb4a18

Introducing, the beginning of development on EVi 10.0. (Intended to leave behind VIm 9.1/9.2.)

[condret@fedi.absturztau.be]

@mrmasterkeyboard did you previously ever commit to vim?

[kkarhan@infosec.space]

@mrmasterkeyboard Q: You also intent to implement #neovim-like #Lua support in lieu of #VimScript?

Cuz I shure as hell would consider adding that (and maybe an #nvChad-like config) to @OS1337 's package wishlist.

[kkarhan@infosec.space]

@mrmasterkeyboard @gllmr so I guess a better #neovim-fork is necessary, too!

[mrmasterkeyboard@mastodon.social]

@condret no, not prior. still, great time to learn!

[mrmasterkeyboard@mastodon.social]

@kkarhan @OS1337 the thought crossed my mind a couple of times... so maybe but i did think of Kuroko however.

[condret@fedi.absturztau.be]

@mrmasterkeyboard as far as i understood the situation, vim maintainer started using AI, because they couldn't handle the amount of work required meanwhile also having a life. so uhm, do what you want, but wouldn*t it be better if more people commited to vim, so that the maintainer would be less stressed?

[mrmasterkeyboard@mastodon.social]

@condret

1. If they can't handle maintaining something like VIm and also have a life, why wouldn't they pass maintainership to someone else?
2. I don't exactly think this looks like not being able handle work and being stressed:
https://hachyderm.io/@AndrewRadev/116175986749599825

https://github.com/vim/vim/pull/19413

Please also note, I'm not also just calling out the lead maintainer, but the other contributors/maintainers/collaborators/whatever they are called for also using AI in a lazy slop way. We don't appreciate dishonesty.

[condret@fedi.absturztau.be]

@mrmasterkeyboard the review thing is just dumb

[dzwiedziu@mastodon.social]

@mrmasterkeyboard This is a site I will watch with dread…

Already there are a few packages that I use or want to use, and at least one that is missing (ntfy).

I need to get on making an IDS ruleset for those, but that's far down on my priority list…

[drchaos@sauropods.win]

@mrmasterkeyboard Just a (stupid) question: I think vim is pretty much there. Has been for a decade or so, I wrote lots of code and research papers using it.
Are there really important features missing?

That said (written): good catch, good initiative.