From: Carsten Dominik <carsten.dominik@gmail.com>
To: Peter Jones <mlists@pmade.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] org-crypt Version 0.3
Date: Tue, 19 May 2009 08:32:31 +0200 [thread overview]
Message-ID: <1DDBCB3C-47F8-4B85-B1B8-6E97274650AA@gmail.com> (raw)
In-Reply-To: <867i0euzxs.fsf@pmade.com>
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.
next prev parent reply other threads:[~2009-05-19 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 16:40 [ANN] org-crypt Version 0.3 Peter Jones
2009-05-18 19:39 ` Scot Becker
2009-05-18 21:25 ` Samuel Wales
2009-05-19 6:32 ` Carsten Dominik [this message]
2009-05-19 10:38 ` Ian Barton
2009-05-20 8:53 ` [ANN] [Solved] " Ian Barton
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=1DDBCB3C-47F8-4B85-B1B8-6E97274650AA@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mlists@pmade.com \
/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).