From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ken manheimer Newsgroups: gmane.emacs.devel Subject: repairing allout auto-save decrypted-topic protection before emacs 24 release Date: Mon, 4 Jul 2011 14:59:44 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=bcaec5215e114db0c404a742f9a6 X-Trace: dough.gmane.org 1309806059 12535 80.91.229.12 (4 Jul 2011 19:00:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 4 Jul 2011 19:00:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 04 21:00:56 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QdoO6-0000th-Vh for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2011 21:00:55 +0200 Original-Received: from localhost ([::1]:38726 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QdoO5-0003zw-Ck for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2011 15:00:53 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50425) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QdoNH-0003oI-1I for emacs-devel@gnu.org; Mon, 04 Jul 2011 15:00:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QdoNF-0001nU-F3 for emacs-devel@gnu.org; Mon, 04 Jul 2011 15:00:02 -0400 Original-Received: from mail-pv0-f169.google.com ([74.125.83.169]:63711) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QdoNF-0001ms-1f for emacs-devel@gnu.org; Mon, 04 Jul 2011 15:00:01 -0400 Original-Received: by pvc12 with SMTP id 12so6006342pvc.0 for ; Mon, 04 Jul 2011 11:59:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=Kt8S4Sq8G1YM6fz7NtwWuEMsHDOPEpeVmmKYtxsdSCc=; b=ruPuQB7daPyTeIKMDhu+CVfLpydddfPyg2MZqh+9ZRmSXCv5L7DVw1wIX6XfTKgEFJ 3APrTlNRQL9F8C5+ijOo/d9fKOg7XyBNh3yBVh7bUb9WyetSWq58Fsi3t7schaT2B/ap EhGh7rtB08FHr0bp91hii61cfgjAZpycM4k4U= Original-Received: by 10.68.4.72 with SMTP id i8mr8504720pbi.269.1309805999140; Mon, 04 Jul 2011 11:59:59 -0700 (PDT) Original-Received: by 10.68.40.40 with HTTP; Mon, 4 Jul 2011 11:59:44 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 74.125.83.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:141550 Archived-At: --bcaec5215e114db0c404a742f9a6 Content-Type: text/plain; charset=ISO-8859-1 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 --bcaec5215e114db0c404a742f9a6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable hi, all. =A0i've discovered a problem with an allout provision to prote= ct against auto-saves of outlines with encrypted topics that are currently = decrypted, and should have a fix soon. =A0however,=A0with the imminent emac= s 24, i wanted to let you know that i'm working on a fix, and hope to c= heck it in before the release happens. =A0i should have the fix done by the= end of the day, and don't expect that the release really is that immin= ent, but figured it wouldn't hurt to mention it.

incidentally, the problem i discovered has to do with the wa= y that auto-save-hook is used. =A0apparently it isn't checked in the co= ntext of each buffer where auto-save is happening, and it offers no provisi= on for gracefully preventing an auto-save per individual buffer, like eg wr= ite-contents-functions does. =A0so i'm going to be transiently settting= buffer-saved-size to -1 while there are decrypted items to exempt such buf= fers from auto-save - should have that done by the end of the day. =A0(sugg= estions about the approach are welcome.)

ken manheimer
--bcaec5215e114db0c404a742f9a6--