That’s what I’m trying to say - in the probably most upsetting way - All of my distros - Ubuntu, Nobara, Debian and so on: all of them have vi as a symlink - only, these days.
As someone who has had to dig into Docker files to debug weird stuff: you’ll be surprised how often vi is still packaged.
It’s in some distros too. Vim is an optional addition to most simple distro installs so you may end up accidentally opening a fallback real vi and get incredibly confused why your shortcuts aren’t working.
I tried to live the “(n)vim is just a verbose way to spell vi” way, but it’s bitten me enough that I’m willing ti type the extra m.
Not all! My arch Linux install definitely has the original vi – the one where when you cw it doesn’t delete the word until you go back to normal mode to save on screen refresh. Plugins? Custom commands? Multiple buffers? Forget it!
More than likely your os is just symlinking vi to vim.
That’s what I’m trying to say - in the probably most upsetting way - All of my distros - Ubuntu, Nobara, Debian and so on: all of them have vi as a symlink - only, these days.
As someone who has had to dig into Docker files to debug weird stuff: you’ll be surprised how often vi is still packaged.
It’s in some distros too. Vim is an optional addition to most simple distro installs so you may end up accidentally opening a fallback real vi and get incredibly confused why your shortcuts aren’t working.
I tried to live the “(n)vim is just a verbose way to spell vi” way, but it’s bitten me enough that I’m willing ti type the extra m.
Not all! My arch Linux install definitely has the original vi – the one where when you
cwit doesn’t delete the word until you go back to normal mode to save on screen refresh. Plugins? Custom commands? Multiple buffers? Forget it!