From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: `org-agenda-get-timestamps' fails on active timestamp before first headline Date: Thu, 24 Jun 2010 08:54:11 +0200 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=57367 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ORgy7-0003yK-Bi for emacs-orgmode@gnu.org; Thu, 24 Jun 2010 03:36:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1ORgup-0001Hw-C0 for emacs-orgmode@gnu.org; Thu, 24 Jun 2010 03:32:04 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:52766) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1ORgup-0001GP-7f for emacs-orgmode@gnu.org; Thu, 24 Jun 2010 03:32:03 -0400 Received: by mail-wy0-f169.google.com with SMTP id 39so365326wyb.0 for ; Thu, 24 Jun 2010 00:32:02 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Erik L. Arneson" Cc: emacs-orgmode@gnu.org Hi Erik, you should not put active time stamps before the first headline. Active time stamps have a specific meaning in Org-mode. Still, I have made the change to catch this error. Greetings - Carsten On Jun 20, 2010, at 10:18 PM, Erik L. Arneson wrote: > 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 > 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 - Carsten