From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: [ANN] org-crypt Version 0.3 Date: Tue, 19 May 2009 08:32:31 +0200 Message-ID: <1DDBCB3C-47F8-4B85-B1B8-6E97274650AA@gmail.com> References: <867i0euzxs.fsf@pmade.com> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M6Jcx-0005TV-UF for emacs-orgmode@gnu.org; Tue, 19 May 2009 03:20:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M6Jct-0005Sp-7I for emacs-orgmode@gnu.org; Tue, 19 May 2009 03:20:43 -0400 Received: from [199.232.76.173] (port=42413 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6Jct-0005Sm-2w for emacs-orgmode@gnu.org; Tue, 19 May 2009 03:20:39 -0400 Received: from mx20.gnu.org ([199.232.41.8]:52756) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M6Jcs-0002FC-MC for emacs-orgmode@gnu.org; Tue, 19 May 2009 03:20:38 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M6Jcs-0006nH-2u for emacs-orgmode@gnu.org; Tue, 19 May 2009 03:20:38 -0400 Received: by mail-ew0-f162.google.com with SMTP id 6so4775367ewy.42 for ; Tue, 19 May 2009 00:20:37 -0700 (PDT) In-Reply-To: <867i0euzxs.fsf@pmade.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Peter Jones Cc: emacs-orgmode@gnu.org On May 18, 2009, at 6:40 PM, Peter Jones wrote: > Sorry for the delays in getting this posted, I've been doing a lot of > traveling lately. > > The attached version of org-crypt fixes a few bugs and is just about > ready to be included in org proper. The only thing it might need > before > inclusion in org is automatic encryption via hooks. > > I'd like to find out how people feel about that. Should org-crypt > attach itself to org-mode-hook so that it can decrypt encrypted > entries > after you open an org file? At first I thought yes, but now I'm > leaning > towards no, you should decrypt entries manually as needed. Yes, I agree. It would be good though to have a function that does it for the entire buffer, just like Scot proposed. And, this function should be ready so that is can safely be stuck into org-mode-hook, for people who want to do automatic decryption. > I do think that org-crypt should hook itself into before-save-hook so > that all entries that *should* be encrypted are encrypted before the > file touches the disk. A user of org-crypt shouldn't have to worry > about setting up a hook, it should just happen automatically. I do agree. Does anyone know how tis will interact with auto-safe? Will the tree be encrypted in my face, when an auto-safe happens.