From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: problem with diary sexps
Date: Tue, 5 Apr 2022 23:06:32 +0700 [thread overview]
Message-ID: <t2hpe9$119m$1@ciao.gmane.io> (raw)
In-Reply-To: <875ynnojvf.fsf@localhost>
On 05/04/2022 18:22, Ihor Radchenko wrote:
> Christian Stuermer writes:
>
>> And the problem is gone, after reverting
>>
>> (result (if calendar-debug-sexp (eval sexp t)
>> (condition-case nil
>> (eval sexp t)
>>
>> back to
>>
>> (result (if calendar-debug-sexp (eval sexp)
>> (condition-case nil
>> (eval sexp)
>>
>> in org-diary-sexp-entry in org.el.
>
> More accurate error can be found after setting calendar-debug-sexp to t.
> I got the following backtrace clearly indicating lexical scope issue:
>
> Debugger entered--Lisp error: (void-variable entry)
> (diary-float t 2 1)
> (let ((entry "") (date '(4 5 2022))) (diary-float t 2 1))
> (eval (let ((entry "") (date '(4 5 2022))) (diary-float t 2 1)) t)
It looks like the source of the problem with unit tests that I faced
yesterday trying to look closer at the bug with daylight saving time in
agenda.
Bad sexp at line 25 in /home/ubuntu/src/org-mode/testing/examples
/agenda-file.org: (let ((entry ) (date '(3 25 2022))) (diary-date 3 25
2022))
((should
(= 3
(count-lines ... ...)))
:form
FAILED 255/900 test-org-agenda/property-timestamp (2.018120 sec)
Emacs-27.3
next prev parent reply other threads:[~2022-04-05 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 15:44 problem with diary sexps Eric S Fraga
2022-04-05 10:28 ` Christian Stuermer
2022-04-05 10:51 ` Eric S Fraga
2022-04-05 11:22 ` Ihor Radchenko
2022-04-05 11:39 ` Eric S Fraga
2022-04-08 2:59 ` Ihor Radchenko
2022-04-08 10:46 ` Eric S Fraga
2022-04-05 16:06 ` Max Nikulin [this message]
2022-10-19 2:30 ` [PATCH] Bind calendar-debug-sexp to non-nil when running tests (was: problem with diary sexps) Ihor Radchenko
2022-11-11 3:36 ` Ihor Radchenko
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='t2hpe9$119m$1@ciao.gmane.io' \
--to=manikulin@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).