From: Kyle Machulis <kyle@nonpolynomial.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: sexp timestamp causing agenda compilation issues as of 8517be79b5c1
Date: Wed, 6 Feb 2013 17:36:22 -0800 [thread overview]
Message-ID: <CAF1EFcersXZYjo-u-YuMxdAaeGa0gaXwSJiUX7ocCaTzwV1_pw@mail.gmail.com> (raw)
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.
next reply other threads:[~2013-02-07 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 1:36 Kyle Machulis [this message]
2013-02-07 9:33 ` sexp timestamp causing agenda compilation issues as of 8517be79b5c1 Bastien
2013-02-07 18:17 ` Kyle Machulis
2013-02-07 18:41 ` Bastien
2013-02-07 20:43 ` Kyle Machulis
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=CAF1EFcersXZYjo-u-YuMxdAaeGa0gaXwSJiUX7ocCaTzwV1_pw@mail.gmail.com \
--to=kyle@nonpolynomial.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).