From: ken manheimer <ken.manheimer@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: repairing allout auto-save decrypted-topic protection before emacs 24 release
Date: Mon, 4 Jul 2011 18:24:46 -0400 [thread overview]
Message-ID: <CAAT_zTGgwzkXp2x3M0wm00fs5N98eUDWfa2_+Ap-bFJ98faLiQ@mail.gmail.com> (raw)
In-Reply-To: <CAAT_zTH+nS8M6-q3Aj=f=9gxuJiQp==v1sc3VMd3dxEPxt2bBw@mail.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 --]
next prev parent reply other threads:[~2011-07-04 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 18:59 repairing allout auto-save decrypted-topic protection before emacs 24 release ken manheimer
2011-07-04 22:24 ` ken manheimer [this message]
2011-07-05 3:35 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAT_zTGgwzkXp2x3M0wm00fs5N98eUDWfa2_+Ap-bFJ98faLiQ@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.