Re: repairing allout auto-save decrypted-topic protection before emacs 24 release

[ken manheimer <ken.manheimer@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

ok, done.  with the bonus that regular file writes with included topics
pending encryption are handled much better, as well.

ken

On Mon, Jul 4, 2011 at 2:59 PM, ken manheimer <ken.manheimer@gmail.com>wrote:

> hi, all.  i've discovered a problem with an allout provision to protect
> against auto-saves of outlines with encrypted topics that are currently
> decrypted, and should have a fix soon.  however, with the imminent emacs 24,
> i wanted to let you know that i'm working on a fix, and hope to check it in
> before the release happens.  i should have the fix done by the end of the
> day, and don't expect that the release really is that imminent, but figured
> it wouldn't hurt to mention it.
>
> incidentally, the problem i discovered has to do with the way that
> auto-save-hook is used.  apparently it isn't checked in the context of each
> buffer where auto-save is happening, and it offers no provision for
> gracefully preventing an auto-save per individual buffer, like eg
> write-contents-functions does.  so i'm going to be transiently settting
> buffer-saved-size to -1 while there are decrypted items to exempt such
> buffers from auto-save - should have that done by the end of the day.
>  (suggestions about the approach are welcome.)
>
> ken manheimer
>

[-- Attachment #2: Type: text/html, Size: 1620 bytes --]