From: Richard Riley <rileyrg@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-reveal (gpg crypt) and auto saving
Date: Fri, 10 Sep 2010 12:26:49 +0200 [thread overview]
Message-ID: <i6d15f$l4a$1@dough.gmane.org> (raw)
In-Reply-To: i6d0mi$aqm$1@dough.gmane.org
Richard Riley <rileyrg@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> On Fri, Sep 10 2010, Richard Riley wrote:
>>
>>> I just opened an org file which has some CRYPT tagged items. When I
>>> org-reveal them (C-c C-r) they are properly decrypted and visible for a
>>> second or two but something is triggering a buffer save which then
>>> causes the "revealed item" to vanish back into gpg haze once more.
>>>
>>> What might be triggering this auto-save? I grepped my code for org-save
>>> but nothing came up.
>>>
>>> Anyone else using this please confirm it does or doesn't happen to
>>> you!
>>
>> Well, this doesn't happen to me, but that's because I use
>> org-decrypt-entry (bound to C-c C-/ at my house) rather than org-reveal.
>> That goes entry by entry, and once they're decrypted, they stay
>> decrypted until I explicitly save the buffer. Maybe you could try that?
>>
>> And if the gods are listening: wouldn't it be nice if
>> org-decrypt-entries (plural) only asked for your passphrase once for a
>> whole buffer, when multiple individual entries were encrypted with the
>> same key? Would that be possible?
>
> It is. It shouldnt have to ask you at all in fact.
>
> gpg-agent.
>
I forgot to add : org-crypt-key.
And my problem solved : it was some junk lying around where I had
experimented with "real-auto-save".
cheers
r.
next prev parent reply other threads:[~2010-09-10 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 9:26 org-reveal (gpg crypt) and auto saving Richard Riley
2010-09-10 9:59 ` Eric Abrahamsen
2010-09-10 10:18 ` Richard Riley
2010-09-10 10:26 ` Richard Riley [this message]
2010-09-10 12:46 ` Eric Abrahamsen
2010-09-10 13:48 ` Richard Riley
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='i6d15f$l4a$1@dough.gmane.org' \
--to=rileyrg@gmail.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 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.