emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Documentation suggestion re: buffers containing crypted entries
Date: Mon, 27 Jun 2011 18:56:54 +0200	[thread overview]
Message-ID: <87wrg7tdpl.fsf@altern.org> (raw)
In-Reply-To: <878vsrxs4g.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 24 Jun 2011 14:42:55 +0100")

Hi Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> 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	other threads:[~2011-06-27 16:56 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 [this message]
2011-06-28 13:29             ` Darlan Cavalcante Moreira
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

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrg7tdpl.fsf@altern.org \
    --to=bzg@altern.org \
    --cc=dave@boostpro.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).