God bless nvi.
I will never understand why people go out of their way to write and maintain such monster configuration files.
Learning core/traditional vi gets one a long way, instead of delusioning themselves with false cleverness and productivity.
I will never understand why people go out of their way to write and maintain such monster configuration files.
Learning core/traditional vi gets one a long way, instead of delusioning themselves with false cleverness and productivity.
My vimrc has slowly accumulated, I add 1 or 2 new keybinds every now and then and I might remove them later if I notice they don't suit my workflow. Most of my changed keybindings are related to making Vim usable with my native keyboard layout (finnish/swedish).
Also per-language additions accumulate over time. The author seems to have put all settings for all file types in the same file.
Learning standard Vi gets you a long way, but sometimes adding or changing a keybind will make things work more fluently.
We often forgot about the essence of things such as typing the actual code or words, and focus on tools. Better investment is learning how to properly type than having countless little helpers which are nothing more than debt.
Increasing complexity in all areas of life really is troublesome.
Let's say you work with splits a lot. Sure you could press ctrl+w all the time, but it's a bit annoying. Rebinding doesn't take much time, but makes it (in the presented example) actually simpler. So did it waste time? A minute or so. Does it make life easier? A little bit. Did the "coding time" suffer? Who cares about a minute or so ;)
When I switched to nvi I realized how wrong I was. My .nexrc contains less than ten lines. There is no syntax highlighting. I was also forced to learn real vi properly. When you do such things amazing things happen.
Sure, you know a lot more than me what makes me productive in my text editor use.
And that is traditional vi. Sure no need to go beyond that. Oh, and 640K should be enough for everybody.