emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Documentation suggestion re: buffers containing crypted entries


From: Darlan Cavalcante Moreira
Subject: Re: [O] Documentation suggestion re: buffers containing crypted entries
Date: Tue, 28 Jun 2011 10:29:20 -0300
User-agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.0 Mule/6.0 (HANACHIRUSATO)

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 <address@hidden> wrote:
> 
> Hi Eric,
> 
> Eric S Fraga <address@hidden> 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.  However, I would suggest that
> > the warning that is in the code be moved into the entry for org-crypt.el
> > in the info manual. 
> 
> I did so -- I added this to the config example in org.texi:
> 
> ,----
> | (setq auto-save-default nil)
> |   ;; Auto-saving does not cooperate with org-crypt.el: so you need
> |   ;; to turn it off if you plan to use org-crypt.el quite often.
> |   ;; Otherwise, you'll get an (annoying) message each time you 
> |   ;; start Org.
> | 
> |   ;; To turn it off only locally, you can insert this:
> |   ;;
> |   ;; # -*- buffer-auto-save-file-name: nil; -*-
> `----
> 
> > Or, as originally proposed, the warning in the code
> > could be wrapped in a customisable variable but this seems like overkill
> > to me.
> 
> To me too, unless we have a clean way to disable auto-save-mode locally.
> 
> > Just my 2ยข!
> 
> 2thx!
> 
> -- 
>  Bastien
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]