I Code With Things and Stuff
blog.raynes.me
blog.raynes.me
I was also going to mention a few other useful Lispy things you can do with vim (like d% to delete an expression), but this page covers them pretty well: http://cybertiggyr.com/15-vim/
I could never leave Emacs at this point, though. Elisp is just too great.
When I originally moved from Vim to Emacs, I found Viper /harder/ than just learning regular ol' Emacs. I assume "Moving parts" refers to exactly the same problems that I had. I could explain more, but it would take time, because I need to figure out some examples instead of explaining my vague impressions of a few years ago.
Point is, as an avid emacs user, I totally get where he is coming from.
I'm not satisfied with:
* tcl/ruby/python interfaces to Vim, because they're horrifically documented, and plugins using these are difficult to distribute
* Re-implementations of a subset of Vim's mountain of hacks in a different language (see jsvim, et al)
The documentation for the interfaces serves as decent reference material. What is really lacking is a long tutorial on the subject that is in an easy to find place.
My favorite example is Command-T. In order to link VimL to C, he had to write a Ruby extension and use the Ruby interface. Which is a total pain.
Also, like I said in the blog post, there is nothing wrong with your setup if you are productive and happy with it.
VimClojure has completion, but it works only when nailgun server is running. Same goes for repl, evaluation and documentation lookup.
I'm a MacVim guy. When working on a project, I exclusively use FuzzyFinder_TextMate and the :edit command. Occasionally I still use cmd+o (primarily when I want to do a one-off file edit and know where the file is "visually" relative to my DropBox folder or something)
Anyway: Here's a Mac tip!
In the native file chooser dialog, simply type ~ or / and the "Go to folder" sub-dialog will slide down and you can type a path! It even has (very primitive) tab completion.
More information: http://www.sublimetext.com/docs/2/osx_command_line.html
The problem for me is the fact that the SLIME REPL offers pretty decent tab-completion
Whereas lein-repl doesn't.
That's the only thing that's sort of keeping me on the EMACS side of the fence