From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Including an active timestamp in encrypted (crypt) org entries Date: Sun, 15 Jan 2012 03:16:52 -0500 Message-ID: <9643.1326615412@alphaville> References: Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:53584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmLH0-00071K-Tg for emacs-orgmode@gnu.org; Sun, 15 Jan 2012 03:17:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RmLGz-0004HJ-M5 for emacs-orgmode@gnu.org; Sun, 15 Jan 2012 03:17:06 -0500 Received: from g1t0028.austin.hp.com ([15.216.28.35]:14745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmLGz-0004Gv-Ga for emacs-orgmode@gnu.org; Sun, 15 Jan 2012 03:17:05 -0500 In-Reply-To: Message from Marcelo de Moraes Serpa of "Sun\, 15 Jan 2012 00\:57\:21 CST." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcelo de Moraes Serpa Cc: nicholas.dokos@hp.com, Org Mode Marcelo de Moraes Serpa wrote: > Hi folks, >=20 > So I timestamp everything I input into my (org-based) GTD system (except = for inbox items, that I'm > sure I will review soon anyway). Here's how I do it: >=20 > * Sample entry > =C2=A0 <2012-01-15 Sun 00:52> >=20 > I have=C2=A0=C2=A0(org-insert-time-stamp nil t nil) bound to C-x C-y and = I just insert it below the entry. This > makes for a nice chronologic history of every data in the system. >=20 > However, I have a problem with encrypted entries. Of course, if I add it = as part of the content to be > encrypted, it will not appear as plain text, but i tried to do like this: >=20 > 1) Create the entry: > =C2=A0 > * Sample Entry >=20 > 2) Write its contents > 3) Tag with :crypt: >=20 > * Sample Entry :crypt: >=20 > 3) Save the buffer. The contents are now encrypted: >=20 > * Sample Entry :crypt: > -----BEGIN PGP MESSAGE----- > Version: GnuPG v1.4.11 (Darwin) >=20 > hQEMA7MmqOB5vxnzAQgAy6tE4lj1uLMaAm8+dPL9N2LHxZsH+VWyiig6gY1rE0M0 > Y1wDLDPYTIR+AUoSMGmU4S+9DZ9v4xoTBev4tjhtZIA9Lvw6aqf3Xlb2YGTJCCeq > ... > -----END PGP MESSAGE----- >=20 > 4) Add the timestamp *before* the --BEGIN PGP MESSAGE-- line: >=20 > * Sample Entry :crypt: > =C2=A0=C2=A0<2012-01-15 Sun 00:52> > -----BEGIN PGP MESSAGE----- > ... >=20 > 5) Save again. >=20 > Expected: Encrypted message and timestamp to stay as is. > What happens: A new encrypted message is written, with the timestamp + th= e "old" encrypted message as > part of it. >=20 > Any hints appreciated :) >=20 Maybe (untried, untested) put the timestamp on the headline?=20 * Sample entry <2012-01-15 Sun 00:52> :crypt: Nick