What's in your .emacs file?
mark_h: http://github.com/markhepburn/dotemacsLots of cruft (roughly 10 years worth), although I did recently start to refactor.Most notable: it's fairly portable and relocatable, thanks to a snippet I cooked up (probably not original, but I haven't seen it else-where):
http://everythingtastesbetterwithchilli.com/initialisation-f...
(check it out anywhere and just symlink init.el to ~/.emacs, it figures out all paths from there.  It'll also load platform-specific code, if you need that).I try and make it lazier by combining autoload and eval-after-load, which helps with startup time.On an organisational point (still work to be done here!), init.el mostly just loads a bunch of other files, which are roughly grouped by task or mode.  Github has been a huge boon, combined with submodules to track a lot of third-party extensions.I don't change many key bindings (most notable is the Yegge-suggested C-w for backward-kill-word), but I do have a /lot/ of extensions installed.  I'm a fairly heavy user, although almost exclusively as an editor (+ lisp or python interaction, etc) -- I don't use it as a mail client, browser, or anything along those lines.  The furthest away I get is the occasional twitter or IRC usage.While I'm rambling: I'd like to make all my key-binding specifications consistent.  Currently I have a mix of string specifications, vectors, kbd macros, etc.  Does anyone know what the canonical approach is these days?  Extra reference: http://www.nongnu.org/emacs-tiny-tools/keybindings/
and http://www.emacswiki.org/emacs/KeyBindingNotation