* sexp timestamp causing agenda compilation issues as of 8517be79b5c1
@ 2013-02-07 1:36 Kyle Machulis
2013-02-07 9:33 ` Bastien
0 siblings, 1 reply; 5+ messages in thread
From: Kyle Machulis @ 2013-02-07 1:36 UTC (permalink / raw)
To: emacs-orgmode
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.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: sexp timestamp causing agenda compilation issues as of 8517be79b5c1
2013-02-07 1:36 sexp timestamp causing agenda compilation issues as of 8517be79b5c1 Kyle Machulis
@ 2013-02-07 9:33 ` Bastien
2013-02-07 18:17 ` Kyle Machulis
0 siblings, 1 reply; 5+ messages in thread
From: Bastien @ 2013-02-07 9:33 UTC (permalink / raw)
To: Kyle Machulis; +Cc: emacs-orgmode
Hi Kyle,
Kyle Machulis <kyle@nonpolynomial.com> 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: )")
> 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.
Thanks for reporting this. Yes, diary sexp are special and can't
really be handled here. I fixed this in master, please confirm this
is okay.
--
Bastien
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: sexp timestamp causing agenda compilation issues as of 8517be79b5c1
2013-02-07 9:33 ` Bastien
@ 2013-02-07 18:17 ` Kyle Machulis
2013-02-07 18:41 ` Bastien
0 siblings, 1 reply; 5+ messages in thread
From: Kyle Machulis @ 2013-02-07 18:17 UTC (permalink / raw)
To: Bastien; +Cc: emacs-orgmode
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 <bzg@altern.org> wrote:
> Hi Kyle,
>
> Kyle Machulis <kyle@nonpolynomial.com> 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: )")
>> 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.
>
> Thanks for reporting this. Yes, diary sexp are special and can't
> really be handled here. I fixed this in master, please confirm this
> is okay.
>
> --
> Bastien
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: sexp timestamp causing agenda compilation issues as of 8517be79b5c1
2013-02-07 18:17 ` Kyle Machulis
@ 2013-02-07 18:41 ` Bastien
2013-02-07 20:43 ` Kyle Machulis
0 siblings, 1 reply; 5+ messages in thread
From: Bastien @ 2013-02-07 18:41 UTC (permalink / raw)
To: Kyle Machulis; +Cc: emacs-orgmode
Kyle Machulis <kyle@nonpolynomial.com> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: sexp timestamp causing agenda compilation issues as of 8517be79b5c1
2013-02-07 18:41 ` Bastien
@ 2013-02-07 20:43 ` Kyle Machulis
0 siblings, 0 replies; 5+ messages in thread
From: Kyle Machulis @ 2013-02-07 20:43 UTC (permalink / raw)
To: Bastien; +Cc: emacs-orgmode
All fixed, thanks!
On Thu, Feb 7, 2013 at 10:41 AM, Bastien <bzg@altern.org> wrote:
> Kyle Machulis <kyle@nonpolynomial.com> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-02-07 20:50 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-07 1:36 sexp timestamp causing agenda compilation issues as of 8517be79b5c1 Kyle Machulis
2013-02-07 9:33 ` Bastien
2013-02-07 18:17 ` Kyle Machulis
2013-02-07 18:41 ` Bastien
2013-02-07 20:43 ` Kyle Machulis
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).