I think we can disable auto-save locally using file variables, but what
org-crypt seem to check is auto-save-default and its value probably won't
change when auto-save is disabled locally.
--
Darlan Cavalcante
At Mon, 27 Jun 2011 18:56:54 +0200,
Bastien wrote:
>
> Hi Eric,
>
> Eric S Fraga w
Hi Eric,
Eric S Fraga writes:
> The question is where should this information be most appropriate to
> appear. In my view, this should be in the documentation (highlighted
> etc), not in the Emacs mini-buffer! I don't know enough texi (any at
> all, actually) so cannot suggest a patch. Howeve
Hi Bill,
Bill Day writes:
> # -*- buffer-auto-save-file-name: nil; -*-
Do you know if this hack works for recent Emacsen without side-effects?
--
Bastien
Bastien writes:
> Eric S Fraga writes:
>
>> I have found this (sit-for 5) annoying enough that I have deleted it
>> from my copy of org. 5 seconds is a large percentage of my emacs start
>> up time!
>
> I just reduced it to one second. Still, the message needs some time to
> appear to the user
Eric S Fraga writes:
> I have found this (sit-for 5) annoying enough that I have deleted it
> from my copy of org. 5 seconds is a large percentage of my emacs start
> up time!
I just reduced it to one second. Still, the message needs some time to
appear to the user.
--
Bastien
Eric S Fraga writes:
> Dave Abrahams writes:
>
>>> I was hit by this last week when I was investigating why my emacs
>>> initialization was taking so long. Later I found out that org-crypt was the
>>
>>> culprit, since it added a "sit for 5s" in order for the user to actually
>>> see this warnin
Dave Abrahams writes:
>> I was hit by this last week when I was investigating why my emacs
>> initialization was taking so long. Later I found out that org-crypt was the
>
>> culprit, since it added a "sit for 5s" in order for the user to actually
>> see this warning.
>>
>> The problem is that or
> I was hit by this last week when I was investigating why my emacs
> initialization was taking so long. Later I found out that org-crypt was the
> culprit, since it added a "sit for 5s" in order for the user to actually
> see this warning.
>
> The problem is that org-crypt tests the value of the a
I was hit by this last week when I was investigating why my emacs
initialization was taking so long. Later I found out that org-crypt was the
culprit, since it added a "sit for 5s" in order for the user to actually
see this warning.
The problem is that org-crypt tests the value of the auto-save-d
I appreciate the warning about encrypted entries, and, I would like to add,
all the hard work and careful thought that has gone into making org-mode
such an incredible piece of software.
I checked the documentation regarding turning off auto-save on pages
containing encrypted entries and saw that
10 matches
Mail list logo
