Eric S Fraga <e.fr...@ucl.ac.uk> writes: > Dave Abrahams <d...@boostpro.com> writes: > >>> 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! > > +1 > > I have found this (sit-for 5) annoying enough that I have deleted it > from my copy of org. 5 seconds is a large percentage of my emacs start > up time!
I also have removed this wait in my local copy of org-mode. I use org-crypt for one subtree in each of my org files which contains passwords and other sensitive data. I rarely decrypt these entries so leaving auto save on for my use case isn't much of a security issue for me. I tend to decrypt the entry, look up the detail I need, and then resave the file which reencrypts the entry immediately. Just my 2 cents :) -- Bernt
