From: Darlan Cavalcante Moreira <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: Dave Abrahams <email@example.com>, firstname.lastname@example.org
Subject: Re: Documentation suggestion re: buffers containing crypted entries
Date: Tue, 28 Jun 2011 10:29:20 -0300 [thread overview]
Message-ID: <email@example.com> (raw)
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.
At Mon, 27 Jun 2011 18:56:54 +0200,
Bastien <firstname.lastname@example.org> wrote:
> Hi Eric,
> Eric S Fraga <email@example.com> 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¢!
next prev parent reply other threads:[~2011-06-28 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 21:34 Documentation suggestion re: buffers containing crypted entries Bill Day
2011-05-02 3:42 ` Darlan Cavalcante Moreira
2011-06-12 20:41 ` Dave Abrahams
2011-06-24 10:04 ` Eric S Fraga
2011-06-24 10:53 ` Bastien
2011-06-24 13:42 ` Eric S Fraga
2011-06-27 16:56 ` Bastien
2011-06-28 13:29 ` Darlan Cavalcante Moreira [this message]
2011-06-24 21:03 ` [PATCH] org-crypt: only warn about auto-save-mode when running org-decrypt Pieter Praet
2011-06-24 21:50 ` Nick Dokos
2011-06-26 6:38 ` Pieter Praet
2011-06-26 8:38 ` [PATCH] org-crypt: make org-decrypt disable auto-save-mode (configurable) Pieter Praet
2011-06-27 16:31 ` [PATCH] org-crypt: only warn about auto-save-mode when running org-decrypt Bastien
2011-06-28 6:55 ` Pieter Praet
2011-06-28 6:57 ` [PATCH] org-crypt: make org-decrypt disable auto-save-mode (configurable) Pieter Praet
2011-06-28 10:04 ` Bastien
2011-06-28 10:05 ` [PATCH] org-crypt: only warn about auto-save-mode when running org-decrypt Bastien
2011-06-24 11:57 ` Documentation suggestion re: buffers containing crypted entries Bernt Hansen
2011-06-27 16:55 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).