I just installed Emacs 24 and, as expected, everything went very well except for the package system, ELPA. I don’t have very many packages that I load with ELPA so at least the number of problems were limited.<\/p>\n
First, following Xah Lee’s Guide on Emacs 24 Package System<\/a> page, I moved the old with<\/p>\n After that change I was able to add Marmalade to the list of package sites.<\/p>\n The next problem was that when I restarted Emacs, I got an error saying it couldn’t load This is annoying because the path will have to be changed when I upgrade. It’s doubly annoying because ELPA worked just fine without having to do this in Emacs 23. Rather than keep dealing with this every time I upgrade one of the problem packages, I added<\/p>\n to my The Emacs 24 ELPA problem appears, from some of the other links I looked at, to be that Emacs 24 deals with the ELPA packages after it has finished processing the Doubtless, this will all be resolved soon so I’m not overly exercised about it. Now that I have things working again, it’s time to explore the new Emacs 24 and see how it improves my life.<\/p>\n Update<\/strong>: Added explicit check for directory when setting paths.<\/p>\n","protected":false},"excerpt":{"rendered":" I just installed Emacs 24 and, as expected, everything went very well except for the package system, ELPA. I don’t have very many packages that I load with ELPA so at least the number of problems were limited. First, following … Continue reading ~\/.emacs.d\/elpa<\/code> directory out of the way and then reloaded my packages. The first problem is that you need to replace the<\/p>\n(when<\/span>\r\n (load\r\n (expand-file-name \"~\/.emacs.d\/elpa\/package.el\"<\/span>))\r\n (package-initialize))<\/pre>\n(require<\/span> 'package<\/span>)<\/pre>\nsmex<\/code>, one of the packages that I load with ELPA. Everything seemed OK: smex<\/code> was loaded onto my machine and seemed fine. The bit of Elisp in init.el<\/code> was what the documentation said it should be but I couldn’t get it to load from init.el<\/code>. I went searching on the Web and after a few useless links I found this page on Emacs 24 Package System Problems<\/a>, again from Xah Lee. In order to get things to work you have to add an explicit load path for some<\/em> of the packages (smex<\/code>, magit<\/code>, dired+<\/code>, and key-chord<\/code> for me). My first pass at this was to add commands to explicitly add the load paths:<\/p>\n(add-to-list 'load-path \"~\/.emacs.d\/elpa\/smex-1.1.2\/\"<\/span>) ; <\/span>XXX Emacs bug<\/span>\r\n(require<\/span> 'smex<\/span>)\r\n(smex-initialize)\r\n(global-set-key (kbd \"M-x\"<\/span>) 'smex)\r\n...<\/pre>\n(defconst<\/span> elpa-loads<\/span> '(\"smex\"<\/span> \"magit\"<\/span> \"dired\"<\/span> \"key-chord\"<\/span>))\r\n(mapc (lambda<\/span> (p) (if<\/span> (file-directory-p p) (add-to-list 'load-path p)))\r\n (directory-files \"~\/.emacs.d\/elpa\"<\/span> t\r\n (concat \"^<\/span>\\\\<\/span>(<\/span>\"<\/span>\r\n (mapconcat 'identity elpa-loads \"<\/span>\\\\<\/span>|<\/span>\"<\/span>)\r\n \"<\/span>\\\\<\/span>)<\/span>.*\"<\/span>)))<\/pre>\ninit.el<\/code>. With that change, the only maintenance required is to add any new problem packages to elpa-loads<\/code>.<\/p>\n.emacs<\/code> or init.el<\/code> file and, therefore the .emacs<\/code> or init.el<\/code> file knows nothing about the packages. That means you can’t set package variables because they haven’t been loaded yet. As far as I could find out, the only solution is to load the files with require<\/code> and that requires that there be a path to the .el<\/code> or .elc<\/code> files.<\/p>\n