New comment by atweiden on void-packages repository

https://github.com/void-linux/void-packages/issues/36164#issuecomment-1068642939

Comment:
> Now an update comes which removes the alternatives and suddenly the user can not run their editor with the vim command and even if they fix it with a shell alias, every program that uses $EDITOR is broken until it's manually fixed.

Equally bad (or worse): running `vim` as root and accidentally getting Neovim instead because of symlinks setup by Void and no other distro under the sun.

It’s a predicament either way.

If you’d allow me to hazard a guess, the group of Void users setting `EDITOR=vim` in a security-critical context and also intending this act to configure *Neovim* to open *instead of actual Vim* is a minority. And assuming this minority even exists, they have to know they’re acting lazily or irresponsibly. Which is fine — but I doubt this hypothetical minority of admins would be overly offended by an announcement from the Void crew stating something to the effect of the Neovim package’s symlinks being removed.

Perhaps the symlinks can be deprecated in an announcement, and removed at a pre-determined time in the future?