Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

All fixed, thanks! On Thu, Feb 7, 2013 at 10:41 AM, Bastien wrote: > Kyle Machulis writes: > >> Updated to 25a481d8, still getting the same error and backtrace when >> generating agendas where the memq block evaluates non-nil. :/ > > Please pull again, it should be fixed now. > > Thanks! > > --

Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

Kyle Machulis writes: > Updated to 25a481d8, still getting the same error and backtrace when > generating agendas where the memq block evaluates non-nil. :/ Please pull again, it should be fixed now. Thanks! -- Bastien

Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

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 wrote: > Hi Kyle, > > Kyle Machulis writes: > >> As of commit 8517be79b5c1fe165d23ea65ad70a282e9c595bb (bisected to >> find t

Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

Hi Kyle, Kyle Machulis 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: )") > s

[O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

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