Vim for developers that use other software, too
cream.sourceforge.net
cream.sourceforge.net
I wonder if I am the only person who feels 'vim shame' (and the closely related 'emacs shame').
'vim shame' - the feeling that you would be a better, more productive coder if only you could master this mysterious editor, but every time you try (about once every couple of years), somewhere between two days and two weeks you find you have drifted back to textmate / sublime editor / eclipse.
For me VIM became main tool when I started to work in multi server environment where all access done through SSH. I could use my most favorite GUI editor Kate to edit files of SSH, but it was less effective due upload/download required.
Do not try to force some tool in your workflow. Instead try it for new tasks/projects and see if it fits naturally. I.e. you should be always aware of other existing technologies, but not forced to use these just because some think it is cool.
Vim isn't compellingly more useful until its ubiquity becomes compellingly useful.
Now I've started to keep my vim config / plugin files in a git repo and deploy them whenever I'm on a new machine. Also as I'm slowly adding new functionality it gets reflected across all environments. I'm hoping this helps this time around.
Disclaimer: I am still conf:ing my .emacs file. :'D
Just to be clear, I'm happy you enjoy your text editor :)
Personally it doesn't matter if you use vim, emacs, Textmate, Sublime, or even Dreamweaver. Whatever you're comfortable with, is what you should use.
I have been a Dreamweaver user since Macromedia made version 4. I then left Windows and went to Ubuntu and started using Gedit... Now I switched to vim... I am by no means a vim god... But I know enough to do what I need to, the rest will come to me with time.
It's not the problem to learn vim, but to unlearn Gimp, Inkscape, etc.
I've used various Vim emulators inside IDEs and they're just not the same as the real thing. If you know Vim well, you end up "typing on eggshells", where every keystroke might cause some unexpected chaos. So it needs to be the real thing.
There is also Vico ( http://www.vicoapp.com/ ) which is a new Mac text editor with vi bindings, and well worth taking a look at.
Caveat emptor: it works with TM bundles, but cannot do vim plugins.
I have tried emacs and vim a few times, but the problem is that I don't want to use them for everything, and I have trouble getting my head around two totally different ways of working. I recently did a check of the programs I use in the average week. The current list is (in no particular order)
* XCode, for Objective-C / iOS development
* Eclipse, for C++ / Android
* Apple Mail
* Chrome
* TeXShop, for Latex editing
* Sublime text, for other bits of C/C++
* Vienna, for RSS reading
* Evernote, for document ordering
* Wunderlist, for todo lists
And what is great is that all these apps share 90% of my frequently used key-presses. In particular, I'm never at a loss as to what quit/find/open/save are. Each of these tools I have found the best at what they do.Vim bindings are used in `less` and `more`. Emacs-style bindings are the default in bash and zsh.
One of these days I might give emacs another go. Last time I had a look for 'quick start' emacs setups (about 3 months ago), the most recent ones I found seemed to be telling me to install the development version of emacs 24, which I couldn't even get to compile.
Unfortunately it lacks a decent text editor.
Right now I'm using Emacs (for the extensibility) with Evil mode (for vim key bindings). I've used vi(m) modes in other editors as well, and some are really good. That's the direction I find more interesting.
On another note, what's the vim-org mode clones looking like lately?