From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Bastien <bzg@altern.org>
Cc: Dave Abrahams <dave@boostpro.com>, emacs-orgmode@gnu.org
Subject: Re: Documentation suggestion re: buffers containing crypted entries
Date: Fri, 24 Jun 2011 14:42:55 +0100 [thread overview]
Message-ID: <878vsrxs4g.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87hb7febzu.fsf@gnu.org> (Bastien's message of "Fri, 24 Jun 2011 12:53:57 +0200")
Bastien <bzg@altern.org> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> 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.
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. Or, as originally proposed, the warning in the code
could be wrapped in a customisable variable but this seems like overkill
to me.
One quickly becomes inured to messages that appear every time you use a
tool. At best, they are simply ignored; at worst, they become annoying,
such as in this case. I'm not complaining critically as it is trivial
to fix for my own use.
Just my 2¢!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.430.g95fa2.dirty)
next prev parent reply other threads:[~2011-06-24 13:43 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 [this message]
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 ` 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=878vsrxs4g.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=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).