3 ms·
Precisely why I use actual vi.. (well.. the nvi rewrite) Unfortunately many current 'vi' users have never actually seen the real thing, since most linuces simp
by cat199 10y ago
Precisely why I use actual vi.. (well.. the nvi rewrite)
Unfortunately many current 'vi' users have never actually
seen the real thing, since most linuces simply alias vi to vim.. I realias it back to nvi because every new vim distro package has a new layer of auto indenting shiny garbage I have to unfiddle before approaching actual vi..
If I want fast text hacking, I use vi. If I want fancy stuff in the sweet spot between basic editor and ide,
I use emacs, and if I want vi key bindings in that sweet
spot, I turn on viper/evil. Done.
- cat199 10y ago^ bitterness resulting from the conflation btw vim and vi :b
- cat199 10y agoalso: keep your grubby hands off of my directory mtimes :D
- ktRolster 10y agovim still opens in ~250 ms (or less) on my system. I'm not sure what problems it's causing you.
- majkinetor 10y agoI have 100++ vim plugins and get around 500ms startup because of contextual loading by neobundle.
- eikenberry 10y agoHis problem were with the extensions vim made to vi and which ones were enabled by default with the packages he used. He never mentioned startup time.
- sevensor 10y agoI first partook of vi on an Irix box under the tutelage of a crusty graybeard. There are some things I do appreciate about vim in contrast. * Syntax highlighting * Unicode * Visual selection * Multiple buffers If I have a task for an editor that doesn't do those things and runs really fast, I usually reach for sed.
- pmoriarty 10y agoSpeaking of needless complexity and bloat, I don't know why you stop at nvi and don't just use ed.