Hi guys, I've discovered a bug in `org-agenda-get-timestamps' wherein an active timestamp before the first headline causes it to fail. I realize that this is probably an error in my use of active timestamps, but there was no really handy error message and this bugged me for weeks.
I'm not familiar enough with org-mode to know what the correct behavior should be here (it'd be nice to get an error message saying "Don't use active timestamps that way!"), but here's an example .org file that will trigger the bug: --8<---------------cut here---------------start------------->8--- #+BEGIN: clocktable :maxlevel 3 :scope today Clock summary at [2010-06-20 Sun 13:09] | L | Headline | Time | |---+---------------------------------------+--------| | | *Total time* | *0:13* | |---+---------------------------------------+--------| | 1 | Track down funky bug <2010-06-20 Sun> | 0:13 | #+END: * Track down funky bug <2010-06-20 Sun> :LOGBOOK: CLOCK: [2010-06-20 Sun 12:43] CLOCK: [2010-06-20 Sun 12:30]--[2010-06-20 Sun 12:43] => 0:13 :END: --8<---------------cut here---------------end--------------->8--- I hope this can help somebody else track down the right place to fix this bug. -- Erik Arneson <dyb...@lnouv.com> GPG Key ID: 1024D/62DA1D25 Office: +1.541.291.9776 Skype: callto://pymander _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
