emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Stuermer <orgmode-ml@recentlyrezzed.de>
To: emacs-orgmode@gnu.org
Subject: Re: problem with diary sexps
Date: Tue, 5 Apr 2022 12:28:47 +0200	[thread overview]
Message-ID: <174462e9-b12f-ca0a-04b5-012bc27b603b@recentlyrezzed.de> (raw)
In-Reply-To: <875ynsq048.fsf@ucl.ac.uk>


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.  I wonder
> if this has anything to do with the changes to the use of advice?
> Nothing else in the recent changes in the git log seem to be relevant.

I've had the same problem after updating org from git with entries like

%%(org-anniversary 2000 4 4) X is %d years old

The commit introducing it is

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.

I wrote about in on Reddit:

Kind regards,

  reply	other threads:[~2022-04-05 10:31 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 [this message]
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
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:

  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=174462e9-b12f-ca0a-04b5-012bc27b603b@recentlyrezzed.de \
    --to=orgmode-ml@recentlyrezzed.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).