From: Memnon Anon <email@example.com> To: firstname.lastname@example.org Subject: [Bug?] org-crypt warning and --daemon Date: Mon, 14 Mar 2011 18:00:09 +0000 (UTC) [thread overview] Message-ID: <email@example.com> (raw) Hi, ,----[ org-crypt.el ] | ;; FIXME Find a better way to encrypt Org auto-saved buffers? | ;; When `auto-save-default' is non-nil, make sure entries are | ;; encrypted before auto-saving | ;; (when auto-save-default | ;; (add-hook | ;; 'org-mode-hook | ;; (lambda () (add-hook 'auto-save-hook 'org-encrypt-entries nil t)))) | | (when auto-save-default | (message "Warning: turn auto-save-mode off in Org buffers containing crypted entries.") | (sit-for 5)) `---- This warning has an unfortunate side-effect when emacs is started as daemon. (sit-for 5), AFAICS, stops the startup ... not only for 5 seconds but permanently. The only way to continue seems to press RET. This RET however, ends up creating a newline in whatever buffer is loaded. Eli suggested this: ,----[ gnu.emacs.help, Message-ID: <firstname.lastname@example.org> ] | 1) modify org-crypt.el to change this: | | (when auto-save-default | | to say | | (when (and (daemonp) auto-save-default) `---- However, this would mean that users who always start as daemon will never actually see it, right? So it may be better to always message the warning but only sit-for when emacs is started as daemon... Or is there any way to make "sit-for" work the intended way both in emacs as well as in emacs --daemon? Memnon ELISP> (emacs-version) "GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)\n of 2010-12-11 on raven, modified by Debian" ELISP> (org-version) "Org-mode version 7.5"
next reply other threads:[~2011-03-14 18:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-14 18:00 Memnon Anon [this message] 2011-03-17 9:31 ` Bastien 2011-03-17 10:14 ` Julien Danjou 2011-03-17 10:18 ` Bastien 2011-03-17 10:19 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Bug?] org-crypt warning and --daemon' \ /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
Code repositories for project(s) associated with this 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).