Closed issue by atweiden on void-packages repository

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

Description:
**Summary**:

The `neovim` template should not install symlinks contesting the `vim` namespace.

**Reasoning**:

1. No other major OS vendor treats Neovim and Vim in this way.

2. In 2022, anyone choosing to open Neovim instead of Vim, or vice versa, is making a very deliberate choice. Because Neovim supports Lua as a first class citizen, while Vim only supports Vimscript as a first class citizen, Neovim’s plugin ecosystem has begun to differ significantly from Vim’s. The Neovim editor is increasingly configured separately from Vim — often in Lua, and with a different selection of plugins.

3. By default, an unconfigured Neovim severely alters the terminal cursor’s appearance in a manner which is difficult to counteract without ending the active terminal session. Accidentally opening an unconfigured Neovim instance upon typing `vim` into a terminal creates an awful user experience — which is precisely what happens when a user installs Neovim after Vim, due to the `neovim` template’s use of `alternatives`.

I’ve been using Vim and Neovim both for a good, long while. To any Neovim fans, I wouldn’t have opened this issue if I didn’t want both programs installed simultaneously. But If I’m typing `vim` in my terminal, I’m most definitely not expecting Neovim to pop open. Type `vim`, and “the” Vim should open, or an error message should appear. At present, due to the `neovim` template’s use of `alternatives`, when you type `vim`, `nvim` pops open instead, and the terminal cursor’s appearance is ruined until you exit the terminal session.