3 ms·
As a vim user, I have to disagree with the "Not vim" part. Learning only vi would lose too many of the advantages of vim. Use vim, learn vim all the way. If/wh
by frederikvs 10y ago
As a vim user, I have to disagree with the "Not vim" part. Learning only vi would lose too many of the advantages of vim.
Use vim, learn vim all the way. If/when you're working on an "old" vi (e.g. the one in busybox, for embedded developers), you'll need to drop some of the more advanced stuff, but you'll still be able to do what you want, edit some config file or such, though it may feel a bit awkward at times.
But when you're doing the heavy editing, you really want to use all of vim.
- bandrami 10y agoDisagree. I'm talking about building basic editor muscle memory and knowing the base set of ex commands that you can use literally anywhere. For that matter I'd say what's really important is that you learn ex.
- WhatIsDukkha 10y agoVi is vim without text objects ie pretty poor (and one of the most important things a vim user should know). Your advice is very misleading in 2016. I don't think there is an active vi codebase, vi is actually vim in compatibility mode in most operating systems.
- bandrami 10y agonvi is actively maintained by the BSDs, which all ship it as the default system editor. Apple did too until IIRC two versions ago.