Org encrypts everything inside a heading with the chosen tag. It does not
try to be smart and decide what should and what should not be encrypted
inside that heading.
Putting the time-stamp in the headline as suggested by others should work,
since org uses that information and the heading itself
Marcelo de Moraes Serpa celose...@gmail.com wrote:
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
[2nd attempt: I think the first one went astray]
Marcelo de Moraes Serpa celose...@gmail.com wrote:
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
Marcelo de Moraes Serpa celose...@gmail.com writes:
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 :)
Put the timestamp in the header.
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
