Vim

Caveat This isn’t very well written, I might revisit this at some point. These are really just my notes in installing emacs and some reasons why I’m going out of the vim world in response to some crazy issues I’m having. I recently decided that I should give Emacs another go. As you might know based on my posts that I really like vim. It’s just simple and easy to find everywhere. Great for sysadmins and programmers alike. What I’ve been finding is the same kind of bloat that I saw in Emacs years before. As I kept adding more languages and features to use Vim as more of an IDE (for clojure specifically), these warts became more apparently. For example, I was segfaulting my vim editor every once in a while while editing Clojure because something odd was happening with my syntax analyzing plugin and the vim buffer. There are additional problems with Vim and Clojure that I found.. say, you absentmindedly wrote a code like this. I use the magnificent Vim Fireplace plugin to code in Clojure. ...

So, the more I use Go, more I like what I’m getting. It’s one of the very few languages that guides you to write better code right off the bat by making it easy and not pedantic. I have a big rant in my head about this but I’ll save you the pain. This was one thing my vim setup was missing. As my go programs became bigger, I kept thinking, I’d really like better autocomplete and, heck, even syntax highlighting. I’ll focus on two ways to do this for vim, one without using Pathogen, Vundle and one using Pathogen ( I don’t use Vundle but the idea is the same ). ...