> I was hit by this last week when I was investigating why my emacs > initialization was taking so long. Later I found out that org-crypt was the > culprit, since it added a "sit for 5s" in order for the user to actually > see this warning. > > The problem is that org-crypt tests the value of the auto-save-default > variable during loading time. This reflects the default behavior and not > the actual auto-save status of the current buffer. > > Maybe a variable to disable this warning could be introduced so that the > user could disable it after understanding the problem.
Oh, yes please! I'm finding the delays introduced by this problem almost intolerable. Call me picky but I've gone to great lengths to make emacs very responsive and this sit-for really interferes! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
