From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Including an active timestamp in encrypted (crypt) org entries
Date: Sun, 15 Jan 2012 00:57:21 -0600 [thread overview]
Message-ID: <CACHMzOF8KT==cyOKiOt3GmBiBfq3vziUmMCSj=rur+eXaPyLtw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Hi folks,
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:
* Sample entry
<2012-01-15 Sun 00:52>
I have (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.
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:
1) Create the entry:
* Sample Entry
2) Write its contents
3) Tag with :crypt:
* Sample Entry :crypt:
3) Save the buffer. The contents are now encrypted:
* Sample Entry :crypt:
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.11 (Darwin)
hQEMA7MmqOB5vxnzAQgAy6tE4lj1uLMaAm8+dPL9N2LHxZsH+VWyiig6gY1rE0M0
Y1wDLDPYTIR+AUoSMGmU4S+9DZ9v4xoTBev4tjhtZIA9Lvw6aqf3Xlb2YGTJCCeq
...
-----END PGP MESSAGE-----
4) Add the timestamp *before* the --BEGIN PGP MESSAGE-- line:
* Sample Entry :crypt:
<2012-01-15 Sun 00:52>
-----BEGIN PGP MESSAGE-----
...
5) Save again.
Expected: Encrypted message and timestamp to stay as is.
What happens: A new encrypted message is written, with the timestamp + the
"old" encrypted message as part of it.
Any hints appreciated :)
- Marcelo.
[-- Attachment #2: Type: text/html, Size: 1894 bytes --]
next reply other threads:[~2012-01-15 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 6:57 Marcelo de Moraes Serpa [this message]
2012-01-15 8:16 ` Including an active timestamp in encrypted (crypt) org entries Nick Dokos
2012-01-15 8:23 ` Nick Dokos
2012-01-15 12:38 ` Richard Riley
2012-01-16 14:27 ` Darlan Cavalcante Moreira
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACHMzOF8KT==cyOKiOt3GmBiBfq3vziUmMCSj=rur+eXaPyLtw@mail.gmail.com' \
--to=celoserpa@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).