From: Bastien <bzg@altern.org>
To: Brian van den Broek <brian.van.den.broek@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: sticky agenda and clock persistence interaction
Date: Fri, 21 Sep 2012 15:37:17 +0200 [thread overview]
Message-ID: <87bogzebua.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAF6DajJgboHkCkBYeNYtbnaj4SiDu1EOTxPb5NcVNuAvsiBjng@mail.gmail.com> (Brian van den Broek's message of "Thu, 20 Sep 2012 22:17:55 -0400")
Hi Brian,
Brian van den Broek <brian.van.den.broek@gmail.com> writes:
> I just found that if I have
>
> (setq org-agenda-sticky t)
> (org-clock-persistence-insinuate)
>
> in my .emacs---or rather in a file that my .emacs invokes with
> load-library---I get
>
> Warning (initialization): An error occurred while loading `/home/brian/.emacs':
>
> Symbol's function definition is void: org-toggle-sticky-agenda
If you are not requiring Org anyhow, org-agenda-sticky will not be
known.
What if you do
(require 'org-install)
(setq org-agenda-sticky t)
(org-clock-persistence-insinuate)
?
> in a *Warnings* buffer, whereas if I have
>
> (org-clock-persistence-insinuate)
> (setq org-agenda-sticky t)
>
> in my .emacs, emacs launches without complaint.
Because org-clock-persistence-insinuate is an autoloaded function.
So calling it will load org-clock.el which will require other Org
packages as well.
> The backtrace from running with --debug-init is attached.
(Btw, there is a suspicious ~/.emacsd/ here -- not ~/.emacs.d/.
Looks weird but maybe that's intentional.)
--
Bastien
next prev parent reply other threads:[~2012-09-21 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 2:17 sticky agenda and clock persistence interaction Brian van den Broek
2012-09-21 13:37 ` Bastien [this message]
2012-09-21 14:32 ` Brian van den Broek
2012-09-21 15:29 ` Bastien
2012-09-21 17:55 ` Achim Gratz
2012-09-22 6:51 ` 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=87bogzebua.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=brian.van.den.broek@gmail.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).