From: Jay Kerns <gjkernsysu@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [Worg] [New Exporter] invalid time specification
Date: Sun, 28 Apr 2013 13:10:16 -0400 [thread overview]
Message-ID: <CAFiLVrbrjAcraKqRt4rwje4xKu7yy9cp9+gOfrM3MNwzt58+MA@mail.gmail.com> (raw)
Hello there,
I've noticed people mentioning on the list that there is a problem
with Worg not publishing, something about an invalid time
specification. Having been publishing Worg locally myself, I noticed
that I was getting a similar error when it came time to construct the
sitemap.org. My workaround at the time was to set "autositemap nil"
in the emacs.el related to Worg, but with Achim's recent improvements
to emacs.el I thought I'd try to track down what's going on. Here is
what I found:
If I reset "autositemap t" in worg-init.el (presumably the same
setting as the Worg server) then near the beginning of interactive
publish I get the following:
,----
| Generating tree-style sitemap for Sitemap for project worg-pages [11 times]
| org-publish-format-file-entry: Invalid time specification
`----
Doing `toggle-debug-on-error' yields (I'm deleting most of it)
,----
| Debugger entered--Lisp error: (error "Invalid time specification")
| format-time-string("%Y-%m-%d" "<2010-04-24 Sat>")
| org-publish-format-file-entry("%t"
"/home/jay/git/worg/org-tutorials/org-latex-export.org"
`----
If I fix the #+DATE: in org-latex-export.org to 2010-04-24 and
republish, then I don't get an error until the next file with the same
problem. :-) Here are the files that generate these errors:
- exporters/beamer/presentation.org [2013-03-13 Wed]
- org-tutorials/non-beamer-presentations.org <2011-06-02 Thu>
- org-tutorials/org-google-sync.org <2011-02-28 Mon>
- org-tutorials/org-outside-org.org <2013-03-12 Di>
- org-tutorials/org-latex-export.org <2010-04-24 Sat>
- org-tutorials/org-meeting-tasks.org <2011-03-30>
- worgmap.org <2013-04-22 Mon>
I have modified the dates on each of those files in the
worg-new-exporter branch and am able to publish successfully even with
"autositemap t". I am not 100% sure that this is the same problem
Worg is having, but if not then it's one heck of a coincidence.
Rather than push my changes to worg-new-exporter, though, maybe this
is something to be fixed somewhere else? What I mean is, the
default #+DATE: inserted by `C-c C-e # default RET' is a date that
looks like <XXXX-YY-ZZ Foo>, and that's the same kind of date which
looks to be tripping up Worg.
I hope this helps with tracking down the problem,
--
Jay
P.S. It looks like I can fix the date with even "2013-03-13 Wed", so
maybe it's the "< >" which is causing the problem.
next reply other threads:[~2013-04-28 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 17:10 Jay Kerns [this message]
2013-04-28 20:11 ` [Worg] [New Exporter] invalid time specification Achim Gratz
2013-04-29 7:41 ` Nicolas Goaziou
2013-04-29 11:49 ` Jay Kerns
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=CAFiLVrbrjAcraKqRt4rwje4xKu7yy9cp9+gOfrM3MNwzt58+MA@mail.gmail.com \
--to=gjkernsysu@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).