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. -- Darlan At Sat, 30 Apr 2011 17:34:06 -0400, Bill Day <williamson....@gmail.com> wrote: > > [1 <text/plain; ISO-8859-1 (7bit)>] > I appreciate the warning about encrypted entries, and, I would like to add, > all the hard work and careful thought that has gone into making org-mode > such an incredible piece of software. > > I checked the documentation regarding turning off auto-save on pages > containing encrypted entries and saw that the warning was repeated but there > was no advice on how to implement it. See > http://orgmode.org/worg/org-tutorials/encrypting-files.html > > My eventual solution (there may be better ones) was to add a line at the top > of my encrypted page as follows: > > # -*- buffer-auto-save-file-name: nil; -*- > > This itself generates a warning every time I go to that page, but it seems > to inhibit auto-save. I would like to suggest that a little bit of > explanation of how to turn auto-save on and off be added to the > documentation on encryption with org-mode. > > Thank you. > > Sincerely, > > Bill Day > > -- > Bill Day > williamson....@gmail.com > [2 <text/html; ISO-8859-1 (quoted-printable)>] >