4 ms·

This is, by far, the most intelligent and useful post I've seen in my attempt to get some answers and understand. I am as hard-headed and as anyone else. I am

This is, by far, the most intelligent and useful post I've seen in my attempt to get some answers and understand. I am as hard-headed and as anyone else. I am also as understanding as anyone else. Change only happens out of necessity and curiosity. I am curious to learn, otherwise I wouldn't spend all this time and take the abuse of some who choose to be total aholes and not take the kind of approach you have taken to at least help someone --not just me, but anyone who may have touched vi and failed-- understand where the strengths may be. Based on your story it is clear that vi is not a weekend project. I am interested in learning so that I can have an opinion that is based on more than the "fuck this" reaction I have had over the last twenty years every time I've touched it on many platforms. I am also impressed by your process and dedication to exploring the space. One can only respect that approach and the conclusion you reached. I too have used a ton of editors. For some reason I've never had the patience to really get into vi. But now I will. Because I owe it to myself to know what everyone is so impressed with. What happens from there is a different matter. Also, thanks for not resorting to insults or calling me a troll as others who never seem to contribute anything of value have done. Thanks again. BTW, if you have more screencast links feel free to share them. I'd appreciate it and I am sure that others who are reading this and might have had the same level of rejection of vi would too.

johncoltrane 14y ago
HTH. There are many screencasts available on the net, paid and free. The best ones happen to be free. Drew Neil's screencasts at http://vimcasts.org/ http://vimcasts.org/ are laser-cut, focused and short. Each video is about one or two specific use-case so you don't get overwhelmed by dozens of "cryptic" commands. The production value is amazing (not in the Michael Bay meaning of the word). Derek Wyatt's Vim Tutorial Videos at http://www.derekwyatt.org/vim/vim-tutorial-videos/ http://www.derekwyatt.org/vim/vim-tutorial-videos/ are the opposite: messy, lighthearted, funny, hysterical and packed with gold nuggets. You'll probably need to watch them a few times if you really want to extract practical knowledge. Peepcode has three Vim-related screencasts but I think they are really bad, specially the "Play-by-Play" one. Yes. Vim is not a weekend project. There's no way you can reach your previous level of productivity in one weekend or two. May I suggest you, based on my own experience, to not install any plugin and not copy someone else .vimrc? Play around with $ vimtutor, exercise on random files (not on serious stuff), read the help (:help<Enter>), watch a bunch of screencasts to get the feel of what it's all about. After the weekend is over you will either be craving for more or be disgusted. Consider both outcomes as a succes and move on to the next step.
- robomartin 14y ago
  Will do. I am planning on hitting-up vimtutor later today after the kids' Saturday activities are over. Fishing trip tomorrow is a priority, so vim will have to take a low priority to real life but I might manage to mess with it at night. Once again, thanks for your input.
  - johncoltrane 14y ago
    So? How did it go?

johncoltrane 14y ago

HTH. There are many screencasts available on the net, paid and free. The best ones happen to be free. Drew Neil's screencasts at http://vimcasts.org/ http://vimcasts.org/ are laser-cut, focused and short. Each video is about one or two specific use-case so you don't get overwhelmed by dozens of "cryptic" commands. The production value is amazing (not in the Michael Bay meaning of the word). Derek Wyatt's Vim Tutorial Videos at http://www.derekwyatt.org/vim/vim-tutorial-videos/ http://www.derekwyatt.org/vim/vim-tutorial-videos/ are the opposite: messy, lighthearted, funny, hysterical and packed with gold nuggets. You'll probably need to watch them a few times if you really want to extract practical knowledge. Peepcode has three Vim-related screencasts but I think they are really bad, specially the "Play-by-Play" one. Yes. Vim is not a weekend project. There's no way you can reach your previous level of productivity in one weekend or two. May I suggest you, based on my own experience, to not install any plugin and not copy someone else .vimrc? Play around with $ vimtutor, exercise on random files (not on serious stuff), read the help (:help<Enter>), watch a bunch of screencasts to get the feel of what it's all about. After the weekend is over you will either be craving for more or be disgusted. Consider both outcomes as a succes and move on to the next step.

robomartin 14y ago
Will do. I am planning on hitting-up vimtutor later today after the kids' Saturday activities are over. Fishing trip tomorrow is a priority, so vim will have to take a low priority to real life but I might manage to mess with it at night. Once again, thanks for your input.
- johncoltrane 14y ago
  So? How did it go?