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
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.
Peter,
I have just been trying out org-crypt. With a minimal org file:
-*- mode: org;
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
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, manually sounds
I think that typically you load a library, then run a function to add
stuff to hooks. That way, loading the library does not have
side-effects. Some packages use the term insinuate.
I'd opt for a default of always encrypting when saving and only
decrypting when manually done. Maybe a little
