Re: [PATCH] Bind calendar-debug-sexp to non-nil when running tests (was: problem with diary sexps)

2022-11-10 Thread Ihor Radchenko
Ihor Radchenko writes: > I guess we can permanently bind calendar-debug-sexp to non-nil in tests. > It should help if we encounter diary-related issues in future. Applied onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c41a2198f2d7a3fbae5953f4b25c84cbe6692e2e --

[PATCH] Bind calendar-debug-sexp to non-nil when running tests (was: problem with diary sexps)

2022-10-18 Thread Ihor Radchenko
Max Nikulin writes: >> 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)))

Re: problem with diary sexps

2022-04-08 Thread Eric S Fraga
On Friday, 8 Apr 2022 at 10:59, Ihor Radchenko wrote: > Should be fixed now in f6813dbe. See Confirmed. Thank you! -- : Eric S Fraga, with org release_9.5.2-426-gf6813d in Emacs 29.0.50

Re: problem with diary sexps

2022-04-07 Thread Ihor Radchenko
Eric S Fraga writes: > On Tuesday, 5 Apr 2022 at 19:22, Ihor Radchenko wrote: >> More accurate error can be found after setting calendar-debug-sexp to t. >> I got the following backtrace clearly indicating lexical scope issue: > > Which makes sense. The diary code does use entry and date as

Re: problem with diary sexps

2022-04-05 Thread Max Nikulin
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

Re: problem with diary sexps

2022-04-05 Thread Eric S Fraga
On Tuesday, 5 Apr 2022 at 19:22, Ihor Radchenko wrote: > More accurate error can be found after setting calendar-debug-sexp to t. > I got the following backtrace clearly indicating lexical scope issue: Which makes sense. The diary code does use entry and date as global variables so really needs

Re: problem with diary sexps

2022-04-05 Thread Ihor Radchenko
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) >

Re: problem with diary sexps

2022-04-05 Thread Eric S Fraga
On Tuesday, 5 Apr 2022 at 12:28, Christian Stuermer wrote: > I've had the same problem after updating org from git with entries like > The commit introducing it is > https://github.com/bzg/org-mode/commit/6d73cd34a07796c33f9435bfc8c9a19e67656c7a > > And the problem is gone, after reverting > >

Re: problem with diary sexps

2022-04-05 Thread Christian Stuermer
Hello! Eric S Fraga writes: I updated org today and now get Bad sexp at line 461 in /home/ucecesf/s/notes/diary.org: (let ((entry ) (date '(4 19 2022))) (diary-float t 2 3)) for a line that looks like <%%(diary-float t 2 3)> This has been in my diary for a very long time with no error.

problem with diary sexps

2022-04-01 Thread Eric S Fraga
Hello all, I updated org today and now get Bad sexp at line 461 in /home/ucecesf/s/notes/diary.org: (let ((entry ) (date '(4 19 2022))) (diary-float t 2 3)) for a line that looks like <%%(diary-float t 2 3)> This has been in my diary for a very long time with no error. I wonder if this