My Emacs config on Github
January 19, 2009 at 05:01 PM | categories: python, emacs | View Comments
The most popular post on this blog is Emacs as a powerful Python IDE. I get quite a few emails regarding that post and I realized the other day that I've done a lot of customizations to my .emacs, and subsequently that post is starting to get a little dated. Time is a curious creature, it seems like yesterday that I wrote that post, but it's been almost 9 months now.
I've been learning and playing around with git recently, so I've decided to post my entire .emacs config on github.
Here are the latest instructions for emulating my Emacs environment on Ubuntu 8.10:
- Enable the universe repository
- sudo apt-get update
- sudo apt-get install emacs-snapshot git-core automake libgconf2-dev texinfo python-setuptools
- cd ~
- git clone git://github.com/EnigmaCurry/emacs .emacs.d
- cd ~/.emacs.d
- git submodule init
- git submodule update
- cd ~/.emacs.d/vendor
- ./vendor-compile.sh
- sudo easy_install "http://downloads.sourceforge.net/rope/rope-0.9.1.tar.gz?modtime=1225268769&big_mirror=0"
- sudo easy_install "http://downloads.sourceforge.net/rope/ropemacs-0.6.tar.gz?modtime=1223039342&big_mirror=0"
I've done some reorganization of the directory structure:
- There actually is no ~/.emacs file anymore, having realized that Emacs looks for ~/.emacs.d/init.el. Convenient!
- All third party packages are now installed in ~/.emacs.d/vendor. This was a great tip I saw in the Emacs Peepcode screencast. (it's $9, but worth it).
- I've taken the suggestion that greg made in the comments to use submodules for some of the vendor packages. The vendor-compile.sh script does the compiling of those packages.
- All private code goes in ~/.emacs.private. This lets me keep passwords and such outside of the main git repository and allows me to publish my config more easily. Before I did this I had to spend time sanitizing the code before each release.
I have appreciated your many encouraging Emails and comments. :)