4 ms·

I want to be good at Vim, but it isn't practical for me at the moment. At work, I've spent the last year and half in Visual Studio or Eclipse (both due to the n

by swanson 15y ago

I want to be good at Vim, but it isn't practical for me at the moment. At work, I've spent the last year and half in Visual Studio or Eclipse (both due to the nature of the projects) and it was really hard for me to switch my brain into "Vim mode" for my own personal stuff. With something as fundamental to the job as a text editor, I have to do it 8 hours a day or it won't stick.

statenjason 15y ago
I actually learned most of my Vim foundations using ViEmu[1] for Visual Studio. While some things are missing, it does an impressive job of emulating Vim and not stepping all over VS and R# (aside from Ctrl-R key bindings). I used the viemu cheat sheet lessons[2] for the learning process. As I became comfortable with the commands in each, I moved on to the next lesson. [1]:http://www.viemu.com/ http://www.viemu.com/ [2]:http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial...
- dekayed 15y ago
  On the Eclipse side, I've been using viPlugin[1]. It is not free, but I've felt like it has been worth the cost since my forays into vim had all failed before getting this plugin. If you're working heavily with Eclipse/VS, it is definitely jarring to switch back and forth between one of those and vim, but using a plugin like this eases that pain. [1] http://www.viplugin.com/viplugin/ http://www.viplugin.com/viplugin/
delwin 15y ago
It took me 5 days to stabilize my workflow in vim, and well worth it. Of course, those were 5 days without too much stress or deadlines, a few weeks ago. I still have a cheat-sheet print out, but am finding myself needing it less and less every day. Although I've been working on fairly small web projects. For larger, corporate-style software development, the transition might be more difficult.

4 ms·

I want to be good at Vim, but it isn't practical for me at the moment. At work, I've spent the last year and half in Visual Studio or Eclipse (both due to the n

by swanson 15y ago

statenjason 15y ago
I actually learned most of my Vim foundations using ViEmu[1] for Visual Studio. While some things are missing, it does an impressive job of emulating Vim and not stepping all over VS and R# (aside from Ctrl-R key bindings). I used the viemu cheat sheet lessons[2] for the learning process. As I became comfortable with the commands in each, I moved on to the next lesson. [1]:http://www.viemu.com/ http://www.viemu.com/ [2]:http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial...
- dekayed 15y ago
  On the Eclipse side, I've been using viPlugin[1]. It is not free, but I've felt like it has been worth the cost since my forays into vim had all failed before getting this plugin. If you're working heavily with Eclipse/VS, it is definitely jarring to switch back and forth between one of those and vim, but using a plugin like this eases that pain. [1] http://www.viplugin.com/viplugin/ http://www.viplugin.com/viplugin/
delwin 15y ago
It took me 5 days to stabilize my workflow in vim, and well worth it. Of course, those were 5 days without too much stress or deadlines, a few weeks ago. I still have a cheat-sheet print out, but am finding myself needing it less and less every day. Although I've been working on fairly small web projects. For larger, corporate-style software development, the transition might be more difficult.