From: Pieter Praet <pieter@praet.org>
To: Christopher Witte <chris@witte.net.au>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Problem with org-crypt
Date: Fri, 02 Sep 2011 10:43:11 +0200 [thread overview]
Message-ID: <874o0v72sg.fsf@praet.org> (raw)
In-Reply-To: <4E5E0744.5080905@witte.net.au>
On Wed, 31 Aug 2011 12:04:52 +0200, Christopher Witte <chris@witte.net.au> wrote:
> Hi all,
>
> I've been using org-crypt and find it a great little addition to
> org-mode, but I have been noticing some weird behaviour. When I'm in a
> file that has NO encrypted entires (or :crypt: tags) and I archive a sub
> tree, I get asked the question "org-decrypt: auto-save-mode may cause
> leakage. Disable it for current buffer?". This must mean
> org-decrypt-entry is being run but I don't understand why. I've noticed
> that org-decrypt-entry is added to the org-reveal-start-hook, I'm not
> sure why that is. When I don't add it to that hook, I no longer get
> asked that question and org-crypt still apears to work as expected, but
> I'm not sure if this will have broken something else.
>
> Does anyone know why org-decrypt-entry is added to the
> org-reveal-start-hook and if it would break anything if I don't add it?
>
> Thanks for the help
> Chris.
>
It's a known issue; Patch available [1].
Bastien's AFK until the 5th, so won't be fixed in mainline before then.
Dropping the `add-hook' line is also a good temporary fix, won't break
anything, only prevents `org-reveal' (`C-c C-r') from decrypting entries.
Peace
--
Pieter
[1] id:"1314539207-15985-1-git-send-email-pieter@praet.org"
next prev parent reply other threads:[~2011-09-02 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 10:04 Problem with org-crypt Christopher Witte
2011-09-02 8:43 ` Pieter Praet [this message]
2011-09-02 8:45 ` Christopher Witte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874o0v72sg.fsf@praet.org \
--to=pieter@praet.org \
--cc=chris@witte.net.au \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.