You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to run cfw:open-org-calendar I get a (wrong-type-argument stringp nil) error.
I won't paste the whole stack trace here, but I did trace the problem back to cfw:org-summary-format and cfw:org-get-timerange, in particular, this let* clause in cfw:org-summary-format:
(extra (cfw:org-tp item 'extra)))
And this one in cfw:org-get-timerange:
(extra (cfw:org-tp text 'extra)))
The problem is that the "extra" variable, in both cases, ends up being nil and is used as part of a string-match call afterwards. The string-match call is expecting a string, not a nil, and so it blows up.
I don't know what the "extra" property is or why it's returning nil or whether it's always done that...if you force the value or extra to be the empty string instead of nil then things seem to load properly, though.
The text was updated successfully, but these errors were encountered:
drivet
changed the title
Cannot run cfw:open-org-calendar (wrong-type-argument stringp nil)
Cannot run cfw:open-org-calendar: (wrong-type-argument stringp nil)
May 25, 2024
Hello,
When I try to run
cfw:open-org-calendar
I get a(wrong-type-argument stringp nil)
error.I won't paste the whole stack trace here, but I did trace the problem back to
cfw:org-summary-format
andcfw:org-get-timerange
, in particular, this let* clause in cfw:org-summary-format:(extra (cfw:org-tp item 'extra)))
And this one in
cfw:org-get-timerange
:(extra (cfw:org-tp text 'extra)))
The problem is that the "extra" variable, in both cases, ends up being nil and is used as part of a
string-match
call afterwards. Thestring-match
call is expecting a string, not a nil, and so it blows up.I don't know what the "extra" property is or why it's returning nil or whether it's always done that...if you force the value or extra to be the empty string instead of nil then things seem to load properly, though.
The text was updated successfully, but these errors were encountered: