From: Carsten Dominik <dominik@science.uva.nl>
To: Jonathan Moore <my.jon.moore@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: "Specified time is not representable" with org-timeline in 4.77
Date: Fri, 15 Jun 2007 07:14:58 +0200 [thread overview]
Message-ID: <76ef38c9d2fb6973c0d58b5a7e9c7ffd@science.uva.nl> (raw)
In-Reply-To: <loom.20070614T230029-253@post.gmane.org>
Fixed, thanks, in particular for the full analysis of this bug.
- Carsten
On Jun 14, 2007, at 23:15, Jonathan Moore wrote:
>
> I am getting an error "Specified time is not representable" when
> calling
> org-timeline. The backtrace looks like:
>
> encode-time(0 0 0 0 0 0 0 0 0)
> apply(encode-time (0 0 0 0 0 0 0 0 0))
> org-time-string-to-time(#("2007-05-10" 0 10 (fontified t mouse-face
> highlight
> rear-nonsticky t keymap (keymap ... ... ... ... ...) face org-date)))
> org-get-all-dates(1 3994 no-ranges t nil 3)
> org-timeline(nil)
> call-interactively(org-timeline)
>
> The problem occurs when org-time-string-to-string calls
> org-parse-time-string.
> This matches with org-ts-regexp1, which has a hard-coded space, so the
> 10-character date string isn't parsed as you'd expect.
>
> (org-parse-time-string "2007-05-10 ") => (0 0 0 10 5 2007 nil nil nil)
> (org-parse-time-string "2007-05-10") => (0 0 0 0 0 0 0 0 0)
>
> A fix might be just to get rid of the space in the regexp.
>
> Best,
> Jon
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
next prev parent reply other threads:[~2007-06-15 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 21:15 "Specified time is not representable" with org-timeline in 4.77 Jonathan Moore
2007-06-15 5:14 ` Carsten Dominik [this message]
2007-06-18 6:55 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76ef38c9d2fb6973c0d58b5a7e9c7ffd@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=my.jon.moore@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).