A painting of me

Text Editor Intervention. ⇒

   5 May 2011, early morning

I use Vim for text editing, and have done so since university. On my Mac I would use TextMate, but I’ve more or less completely given it up for MacVim. For myself this wasn’t such a big deal. I never got particularly good at using all of TextMate’s features, since I used Vim far more for programming. TextMate is a nice editor, and remains a nice editor, but it’s incredibly slow compared to Vim. It also chokes on large files, which can be a big nuisance. (I always had to have another editor around to open big SQL dumps, for example.)

This is a post from my link log: If you click the title of this post you will be taken the web page I am discussing.

Perma-Link  

Comments

  1. Have you checked out vico? http://www.vicoapp.com

  2. Yeah, he mentions it in the article and i’ve seen it linked around elsewhere. Looks promising, but I don’t know if it’s so much better than just using regular Vim.

  3. I’ve been giving Vico a test-drive today and comparing it to my MacVim setup.

    upside:

    - sidebar is way nicer than NERDTree

    - sidebar fuzzy search (dunno how it compares to TextMate or PeepOpen)

    - split windows + vim navigation for them

    - symbol list<br>

    - smart case-insensitive search

    downside:

    - can’t switch tabs using Cmd-Shift-[ (could probably find a way to map this though)

    - no highlight/underline for matches when searching

    - :s doesn’t work

    - :e in split window opens new tab

    - no rails.vim

    I’d say it’s 80-90% of the way to what I need, which is not bad considering it’s not finished yet. YMMV depending on the complexity of your vim usage.

  4. Interesting. I think i’ll give it a try. I don’t think my Vim setup is particularly crazy, but I guess i’ll find out after trying Vico out.

  5. Updates:

    Key mapping: http://blog.vicoapp.com/2011/05/Macros-and-key-bindings

    New window opening: http://twitter.com/#!/vicoapp/status/66378503758684160

    You can hack :s with “!r sed s/foo/bar/” which isn’t optimal but works

Don't be shy, you can comment too!

 
Some things to keep in mind: You can style comments using Textile. In particular, *text* will get turned into text and _text_ will get turned into text. You can post a link using the command "linktext":link, so something like "google":http://www.google.com will get turned in to google. I may erase off-topic comments, or edit poorly formatted comments; I do this very rarely.