More info: This appears to be failing in org-parse-time-string, when it compares the string "<now>" to org-ts-regexp0 Nothing in the regexp nor in the call tree is attempting to process the special time values.
It seems like there is missing code needed either in org-parse-time-string to handle the special strings, or in the clock-updater code to convert the special time strings to actual times before passing them on. Is there somewhere else I should be submitting this bug? On Wed, May 8, 2013 at 4:47 PM, Subhan Tindall < subhan.tind...@rentrakmail.com> wrote: > The following clocktable line: > #+BEGIN: clocktable :tstart "<-7d>" :tend "<now>" > > #+END: > > errors out on the tstart & tend times > According to all the documentation I can find, these are both valid > 'special' time strings. > Attempts to evaluate the clocktable with C-c C-c give the error: > > Updating dynamic block `clocktable' at line 57... > org-parse-time-string: Not a standard Org-mode time string: <-7d> > > however this: > #+BEGIN: clocktable :tstart "<2013-05-08 Wed>" :tend "<2013-05-09 Thu>" > #+END: > > works just fine > > > -- > Subhan Michael Tindall | Software Developer > | s...@rentrakmail.com > RENTRAK | www.rentrak.com | NASDAQ: RENT > -- Subhan Michael Tindall | Software Developer | s...@rentrakmail.com RENTRAK | www.rentrak.com | NASDAQ: RENT
