emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Jones <mlists@pmade.com>
To: emacs-orgmode@gnu.org
Subject: [ANN] org-crypt Version 0.3
Date: Mon, 18 May 2009 10:40:47 -0600	[thread overview]
Message-ID: <867i0euzxs.fsf@pmade.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

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.

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.

Any suggestions on the best way to make that happen in org-crypt?


[-- Attachment #2: org-crypt.el --]
[-- Type: application/emacs-lisp, Size: 5612 bytes --]

[-- Attachment #3: Type: text/plain, Size: 65 bytes --]


-- 
Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US

[-- Attachment #4: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2009-05-18 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 16:40 Peter Jones [this message]
2009-05-18 19:39 ` [ANN] org-crypt Version 0.3 Scot Becker
2009-05-18 21:25 ` Samuel Wales
2009-05-19  6:32 ` Carsten Dominik
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=867i0euzxs.fsf@pmade.com \
    --to=mlists@pmade.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).