EDIT: I updated the fork to last commit before the AI slop.
-
@mrmasterkeyboard@mastodon.social @lu_leipzig@troet.cafe VEx would be bad because vex(v) means to annoy in english
EVi's acronym being up to interpretation sounds...kinda funny and good
EVi and Vimpression... hard to decide. Those are my final two.
-
@mrmasterkeyboard Erk... Thanks for the link.
-
EVi and Vimpression... hard to decide. Those are my final two.
@thing @lu_leipzig How about Vimprovisation?
-
@thing @lu_leipzig How about Vimprovisation?
@mrmasterkeyboard @thing Anything with "vim" in the name is asking for trouble, trademark-wise.
-
@mrmasterkeyboard @thing Anything with "vim" in the name is asking for trouble, trademark-wise.
@lu_leipzig @thing didn't think it was trademarked, but I guess we'll go with EVi then. Excellent Vi.
-
@lu_leipzig @thing didn't think it was trademarked, but I guess we'll go with EVi then. Excellent Vi.
@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. -
@lu_leipzig @thing didn't think it was trademarked, but I guess we'll go with EVi then. Excellent Vi.
@lu_leipzig @thing (another reason why i picked EVi, it sounds like VMware's ESXi.)
-
@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.@thing @lu_leipzig Easy Vi, Extended Vi, Electric Vi, Elected Vi, Eradicated Vi, Everybody (yeeeaaaah!) Vi, Every Vi
-
@thing @lu_leipzig Easy Vi, Extended Vi, Electric Vi, Elected Vi, Eradicated Vi, Everybody (yeeeaaaah!) Vi, Every Vi
@mrmasterkeyboard@mastodon.social @lu_leipzig@troet.cafe yeah, like that :)
-
@mrmasterkeyboard@mastodon.social @lu_leipzig@troet.cafe yeah, like that :)
-
EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.
hard-forked vim at release 9.1.0 (Jan 2024)
https://codeberg.org/NerdNextDoor/vim
maybe we can get a group of people behind this??
Fuck AI.
@mrmasterkeyboard I would like to have a vim that is Bram's vim, maintained forever. Feature freeze.
-
Updated my fork to 9.1.2073 before the release of it, specifically, the last commit before the AI commit.
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.)
-
EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.
hard-forked vim at release 9.1.0 (Jan 2024)
https://codeberg.org/NerdNextDoor/vim
maybe we can get a group of people behind this??
Fuck AI.
@mrmasterkeyboard did you previously ever commit to vim? -
EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.
hard-forked vim at release 9.1.0 (Jan 2024)
https://codeberg.org/NerdNextDoor/vim
maybe we can get a group of people behind this??
Fuck AI.
@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.
-
@mrmasterkeyboard @gllmr so I guess a better #neovim-fork is necessary, too!
-
@mrmasterkeyboard did you previously ever commit to vim?
@condret no, not prior. still, great time to learn!
-
@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.
-
@condret no, not prior. still, great time to learn!
@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 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?
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/116175986749599825https://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.
-
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/116175986749599825https://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.
@mrmasterkeyboard the review thing is just dumb