From: Karl Voit <devnull@Karl-Voit.at>
Subject: org-agenda-sticky -> Recursive load (was: Agenda hides timestamp)
Date: Sun, 2 Sep 2012 14:30:24 +0200 [thread overview]
Message-ID: <2012-09-02T14-25-15@devnull.Karl-Voit.at> (raw)
* Bastien <firstname.lastname@example.org> wrote:
> Karl Voit <devnull@Karl-Voit.at> writes:
>> I'd like to see this entry on my agenda according to its timestamp
>> at least when I also add [A]rch-files and probably [L]og-all.
>> For now, it never shows up.
> I cannot reproduce the problem with emacs -Q and your settings,
> it shows up with a simple M-x org-agenda RET a
> Can you try with emacs -Q and confirm we need to further investigate
> your file/config?
emacs -Q does not even know Org at my side :-)
Nevertheless, the problem is somewhere completely different. When I
started with --debug-init I recognized an error «Recursive load:
...» of several elc files.
This does not show up, when I disable «(setq org-agenda-sticky t)».
In that case, I get the desired behavior with the foo bar event
showing up on my agenda.
I checked out the latest git version and can reproduce this issue.
I am unsure if this is my configuration being copy&paste of things I
do not completely understand or a bug :-(
I can live without a sticky agenda but I am also happy to help
narrowing down the problem, if it is a bug.
next prev parent reply other threads:[~2012-09-02 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 10:46 Agenda hides timestamp Karl Voit
2012-09-02 11:00 ` Bastien
2012-09-02 12:30 ` Karl Voit [this message]
2012-09-02 12:49 ` org-agenda-sticky -> Recursive load Karl Voit
2012-09-02 21:06 ` Bastien
2012-09-02 21:05 ` Bastien
2012-09-02 21:33 ` Thomas S. Dye
2012-09-14 6:11 ` Bastien
2012-09-14 15:23 ` Thomas S. Dye
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).