emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Dave Abrahams <dave@boostpro.com>, emacs-orgmode@gnu.org
Subject: Re: Documentation suggestion re: buffers containing crypted entries
Date: Fri, 24 Jun 2011 07:57:01 -0400	[thread overview]
Message-ID: <87y60rsar6.fsf@norang.ca> (raw)
In-Reply-To: <8762nv5yvf.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 24 Jun 2011 11:04:36 +0100")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Dave Abrahams <dave@boostpro.com> 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 org-crypt tests the value of the auto-save-default
>>> variable during loading time. This reflects the default behavior and not
>>> the actual auto-save status of the current buffer.
>>>
>>> Maybe a variable to disable this warning could be introduced so that the
>>> user could disable it after understanding the problem.
>>
>> Oh, yes please!  I'm finding the delays introduced by this problem
>> almost intolerable.  Call me picky but I've gone to great lengths to
>> make emacs very responsive and this sit-for really interferes!
>
> +1
>
> 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 also have removed this wait in my local copy of org-mode.  I use
org-crypt for one subtree in each of my org files which contains
passwords and other sensitive data.  I rarely decrypt these entries so
leaving auto save on for my use case isn't much of a security issue for
me.  I tend to decrypt the entry, look up the detail I need, and then
resave the file which reencrypts the entry immediately.

Just my 2 cents :)
-- 
Bernt

  parent reply	other threads:[~2011-06-24 11:57 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
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       ` Bernt Hansen [this message]
2011-06-27 16:55 ` Documentation suggestion re: buffers containing crypted entries 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=87y60rsar6.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=dave@boostpro.com \
    --cc=e.fraga@ucl.ac.uk \
    --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).