Hi Pieter,
Pieter Praet writes:
> 2 lessons I've learned today:
> - DON'T test this stuff in a *scratch* buffer (seriously...)
> - DO consume sufficient quantities of coffee (IOW, org-encrypt-entries
> doesn't encrypt entries unless they're *tagged* to be)
:)
>> I'm not confident in disablin
On Mon, 27 Jun 2011 18:31:58 +0200, Bastien wrote:
> Hi Pieter,
>
> Thanks for the patch at the end of this thread.
>
> Pieter Praet writes:
>
> > Ideally, we'd have a defcustom `org-crypt-auto-save' with the following
> > options:
> > - 'ask : Ask the user whether or not to decrypt the e
Hi Pieter,
Thanks for the patch at the end of this thread.
Pieter Praet writes:
> Ideally, we'd have a defcustom `org-crypt-auto-save' with the following
> options:
> - 'ask : Ask the user whether or not to decrypt the entry.
> - 'disable : Disable auto-save-mode for the current buffer bef
On Fri, 24 Jun 2011 17:50:04 -0400, Nick Dokos wrote:
> Pieter Praet wrote:
>
> > As auto-save-mode can only cause leakage after org-decrypt has been run,
> > there's no need to check for it (and potentially cause annoyance) so early.
> >
> > Unfortunately, auto-save-mode doesn't set a buffer-l
Pieter Praet wrote:
> As auto-save-mode can only cause leakage after org-decrypt has been run,
> there's no need to check for it (and potentially cause annoyance) so early.
>
> Unfortunately, auto-save-mode doesn't set a buffer-local var to indicate
> whether it's enabled for the current buffer
As auto-save-mode can only cause leakage after org-decrypt has been run,
there's no need to check for it (and potentially cause annoyance) so early.
Unfortunately, auto-save-mode doesn't set a buffer-local var to indicate
whether it's enabled for the current buffer (checking
`buffer-auto-save-file
