emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian van den Broek <brian.van.den.broek@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: sticky agenda and clock persistence interaction
Date: Fri, 21 Sep 2012 10:32:36 -0400	[thread overview]
Message-ID: <CAF6DajKiL+MOC3Ze331dRUE=tSemZR+zXZydn_Yb-ANjJkAytg@mail.gmail.com> (raw)
In-Reply-To: <87bogzebua.fsf@bzg.ath.cx>

On 21 September 2012 09:37, Bastien <bzg@altern.org> wrote:
> 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)
>
> ?

Hi Bastien,

(After the bad website report, I'm pleased to see I've not done
anything so silly this time :-)

I have a file, ogrconf.el that gets loaded by my .emacs. It starts
with (require 'org-install). So, the error I reported emerged from
what you suggest, save that I have a few hundred lines of config
between the require and the sticky and persistence lines.

I just tested, and if I start out my orgconf.el with

(require 'org-install)
(setq org-agenda-sticky t)
(org-clock-persistence-insinuate)

(thus, putting the relevant lines before any of my other org
configuration) I get the same warning I reported in the original post.
I've not done the backtrace assuming that the same warning with pretty
much the same cause would have the same backtrace; I'm happy to
provide if it is wanted.

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

It's intentional. At some point, my .emacs became unwieldy. I
separated my config into a bunch of files which .emacs loads and put
them into a user-created dir ~/.emacsd,  leaving ~/.emacs.d for emacs
to have its way with. I prefer to enforce separation between files I
administer and those under emacs's control.

Best,

Brian

  reply	other threads:[~2012-09-21 14:33 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
2012-09-21 14:32   ` Brian van den Broek [this message]
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='CAF6DajKiL+MOC3Ze331dRUE=tSemZR+zXZydn_Yb-ANjJkAytg@mail.gmail.com' \
    --to=brian.van.den.broek@gmail.com \
    --cc=bzg@altern.org \
    --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).