I am getting this message during startup of my Emacs, recently (since the update to Emacs 26?). I could not track down where is package is loaded and did not find anything related to this message in the web. It is not really a problem but I would like to know why my Emacs loads an obsolete package.

  • It may be surprising, but it's far from unusual to use packages that didn't get the memo yet. Figuring this out is something you'll have to do yourself, by testing whether you get the same message with emacs -q / emacs -Q, then bisecting towards the offending part of your init / site file. – wasamasa Jul 1 '18 at 10:03
  • I was hoping someone already did this ;-) Then I will see, when I find the time and track down the „problem“. – Martin Buchmann Jul 1 '18 at 10:10
  • Sorry for posting this as an answer, but I am not allowed to post comments yet and this post was so relevant that asking a new question didn't feel any better than this and it might have never attracted the attention of Martin Buchmann... From Martin Buchmann's comments: > It was indeed an old version of mu4e. Making sure that the recent version is loaded everything is fine @Martin Buchmann: may I ask you how you did this? I am having the exact same issue, but it seems that I am using the most recent version of mu/mu4e (from May 31 as shown [here](archlinux.org/packages/community – prosoitos Jul 8 '18 at 21:38
  • @prosoitos I am using macports on macOS and there is a mu-devel port which works for me. I not sure which package you could use on your system. But you could a) wait until your system is updated or b) try to get the most recent commit using git. – Martin Buchmann Jul 9 '18 at 4:28

Add this to the top of your .emacs, you should get a backtrace when it loads:

(defun debug-on-load-obsolete (filename)
  (when (equal (car (last (split-string filename "[/\\]") 2))
(add-to-list 'after-load-functions #'debug-on-load-obsolete)
  • That helped a lot! I could track down the loading to mu4e and will investigate it further. – Martin Buchmann Jul 1 '18 at 17:41
  • 1
    It was indeed an old version of mu4e. Making sure that the recent version is loaded everything is fine. – Martin Buchmann Jul 6 '18 at 14:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.