<p>Yes, I promise I’ll shut up about Emacs package management via ELPA any minute now.</p>

<p>I’ve blogged about a little elisp snippet I use to install my preferred base set of Emacs packages <a href="https://www.lonecpluspluscoder.com/2014/09/06/install-your-basic-emacs-packages-via-a-single-function-call/" title="Install your basic Emacs packages via a single function call">before</a>. Thanks for all the feedback, it definitely helped improve the code.</p>

<p><a href="http://melpa.org/">MELPA</a> has recently got its own domain (<a href="http://melpa.org/">melpa.org</a>) so it’s time to update your list of package repositories with the new URL.</p>

<p>If you, like me tend to carry around or “cloud around” a single .emacs file so you end up with similar environments wherever you have an Emacs install, you know it’s a little painful to ensure that you have the same set of basic packages installed on each one of your Emacs installations. As I had mentioned before I don’t use that many third party packages so my Emacs configurations aren’t that complicated, but I always prefer to have the computer remember things…