From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kyle Machulis <kyle@nonpolynomial.com>
Subject: Re: sexp timestamp causing agenda compilation issues as of
 8517be79b5c1
Date: Thu, 7 Feb 2013 10:17:29 -0800
Message-ID: <CAF1EFcededybtY1WdrXdRJz8jV_ys87ACpxv6JVKUsgFJRW==w@mail.gmail.com>
References: <CAF1EFcersXZYjo-u-YuMxdAaeGa0gaXwSJiUX7ocCaTzwV1_pw@mail.gmail.com>
	<87a9rg1n9v.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:49570)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kyle@nonpolynomial.com>) id 1U3W2O-000314-8b
	for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 13:17:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kyle@nonpolynomial.com>) id 1U3W2M-0005oY-FH
	for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 13:17:32 -0500
Received: from mail-ve0-f169.google.com ([209.85.128.169]:59192)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kyle@nonpolynomial.com>) id 1U3W2M-0005oQ-Aj
	for emacs-orgmode@gnu.org; Thu, 07 Feb 2013 13:17:30 -0500
Received: by mail-ve0-f169.google.com with SMTP id 15so2660367vea.28
	for <emacs-orgmode@gnu.org>; Thu, 07 Feb 2013 10:17:29 -0800 (PST)
In-Reply-To: <87a9rg1n9v.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>

Updated to 25a481d8, still getting the same error and backtrace when
generating agendas where the memq block evaluates non-nil. :/

On Thu, Feb 7, 2013 at 1:33 AM, Bastien <bzg@altern.org> wrote:
> Hi Kyle,
>
> Kyle Machulis <kyle@nonpolynomial.com> writes:
>
>> As of commit 8517be79b5c1fe165d23ea65ad70a282e9c595bb (bisected to
>> find this), agenda compilation died with the following backtrace for
>> me:
>>
>> Debugger entered--Lisp error: (error "Bad timestamp `'
>> Error was: (Not a standard Org-mode time string: )")
>>   signal(error ("Bad timestamp `'\nError was: (Not a standard Org-mode
>> time string: )"))
>>   error("Bad timestamp `%s'%s\nError was: %s" "" "" ("Not a standard
>> Org-mode time string: "))
>>   byte-code(...)
>>   org-time-string-to-absolute("")
>>   byte-code(...)
>>   org-agenda-get-timestamps(nil)
>>   org-agenda-get-day-entries("~/emacs_org/mozilla/mozilla.org" (2 6
>> 2013) :deadline :scheduled :timestamp :sexp)
>>   apply(org-agenda-get-day-entries "~/emacs_org/mozilla/mozilla.org"
>> (2 6 2013) (:deadline :scheduled :timestamp :sexp))
>>   byte-code(...)
>>   byte-code(...)
>>   org-agenda-list(nil)
>>   call-interactively(org-agenda-list)
>>   byte-code(...)
>>   org-agenda(nil)
>>   call-interactively(org-agenda nil nil)
>>
>> It's dying when it hits a headline as follows:
>>
>> * Meeting 13:30
>> , <%%(memq (calendar-day-of-week date) '(3))>
>>
>> I'm guessing this has something to do with the agenda sorting updates
>> in the commit not liking the fact that the sexp evaluates to true. If
>> the sexp evaluates nil for the day the agenda is trying to parse,
>> nothing happens. If it evaluates to something other than nil (t if I
>> use (= 3 (calendar-day-of-week date)), 3 if I use memq on a wednesday,
>> etc...), I get the above error.
>
> Thanks for reporting this.  Yes, diary sexp are special and can't
> really be handled here.  I fixed this in master, please confirm this
> is okay.
>
> --
>  Bastien