So at my new job, the main development machines are Macs. Previously, I knew a ton of people doing Windows development on Macs though most of the work was done in Parallels, Fusion or Bootcamp. I haven’t been on a Mac since probably sixth grade when I wrote a program I didn’t find on the internet to output Alfred E. Neuman’s face to the terminal. Suffice it to say, I’m out of touch. So I spent 2 hours yesterday just trying to get MacVim installed and bent to my will. This series (where series may be anywhere from 1 to N posts) will throw little tidbits of knowledge out into the interwebs regarding my trials and tribulations with becoming a Mac convert. This will be old hat for anyone with any Linux or Mac background but for someone coming from a purely Windows environment with only a tiny bit of self-taught Linux history, maybe it will help other total beginners.
Lesson 1 involves getting MacVim to correctly recognize Python files with pretty indenting and whatnot. I downloaded MacVim and so far have just left it in the Downloads folder which I’m sure is ridiculous but at least I know where it is. Once that was done, I spent a ton of time getting a .vimrc file set up, mostly because files starting with . on a Mac are system files and hidden by default. This page helped a lot in that regard.
Once that was done, I set about getting MacVim to deal with Python files with pretty indenting and whatnot. One thing to understand right off the bat with MacVim is that “filetype”, “plugin” and “indent” are disabled by default on installation. Before you go creating your own plugin files and indent files, it’s helpful to add “filetype plugin indent on” to your settings file and see what happens. You may not go to the trouble I did overwriting all the defaults. But that’s just how I roll.
I found this helpful post dealing with Python syntax and indenting. The key is figuring out where to put those files. When you install MacVim (or lots of other apps on the Mac), you get a folder typically named
Now if I could just remember that on a Mac keyboard, you copy and paste using the Command key instead of the control key, I’d be set up.
2 comments on “My New Mac Travails Part I”
January 11, 2010 at 11:40 am
Don’t modify the files under MacVim.app. They’ll get overwritten if/when you ever upgrade it. You ought to be able to do those customizations in your home dir as .vimrc or similar.
January 12, 2010 at 9:20 am
Thanks for the tip Greg, that’s definitely the kinds of things I’m looking for as I dip my feet into the extremely cold water (to me) of the Mac. I like it so far but there’s a learning curve.
I went ahead and just uninstalled MacVim and reinstalled it to make sure it was clean. I’ve updated my .vimrc file and it’s working well. Now if I can just get VimClojure installed, I’ll be in business.