emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alexander Lazarević" <laza@e11bits.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] BBDB anniversary entries with a format-string produce error [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.4/lisp/org/)]
Date: Mon, 14 Oct 2024 01:46:30 +0000	[thread overview]
Message-ID: <CAMPYxd=iUwLp0cKFNcrcABZ495eh0rziKeE3KjQmdwY6PWzfQg@mail.gmail.com> (raw)
In-Reply-To: <878qutsd1v.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

I tried the following but no stack-trace is produced:

rm -rf .emacs .emacs.d
cat > /tmp/agenda.org << orgfile
* Anniversaries
:PROPERTIES:
#+CATEGORY: Ann
:END:
%%(org-bbdb-anniversaries-future 3)
orgfile

emacs

package-install bbdb
bbdb-create
Just some name
(i)nsert a field "anniversary" for that record
with content "1998-mm-dd something" and month/day of next day
(s)ave the bbdb file
find-file /tmp/agenda.org
org-agenda-file-to-front
customize-option calendar-debug-sexp toggle on
org-agenda

Message: Args out of range: 52, 55

Agenda looks like this:

Week-agenda (W42):
Monday     14 October 2024 W42
  Ann:        somethi -- tomorrowng



On Sat, 12 Oct 2024 at 12:45, Ihor Radchenko <yantar92@posteo.net> wrote:

> Alexander Lazarević <laza@e11bits.com> writes:
>
> > In one agenda (personal.org) I have the following entry:
> >
> > * Anniversaries
> > :PROPERTIES:
> > #+CATEGORY: Ann
> > :END:
> > %%(org-bbdb-anniversaries-future 3)
> >
> > This works for BBDB entries that have an anniversary like "1973-06-22"
> > or "2021-04-91 wedding", but it fails for something like "1998-03-12 %s
> > created bbdb-anniv.el %d years ago" (from the examples in ol-bbdb.el).
> >
> > The error message is:
> >
> > Bad sexp at line 5 in /home/laza/exobrain/org/personal/personal.org:
> (let
> > ((entry ) (date '(10 8 2024))) (org-bbdb-anniversaries-future 3))
>
> Please set `calendar-debug-sexp' to t and try to build agenda again.
> Emacs will then produce an actual backtrace, detailing where the error
> is.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>

[-- Attachment #2: Type: text/html, Size: 3052 bytes --]

  reply	other threads:[~2024-10-14  1:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 17:14 [BUG] BBDB anniversary entries with a format-string produce error [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.4/lisp/org/)] Alexander Lazarević
2024-10-12 12:47 ` Ihor Radchenko
2024-10-14  1:46   ` Alexander Lazarević [this message]
2024-10-14 18:49     ` Ihor Radchenko
2024-10-15  5:21       ` Alexander Lazarević
2024-10-15 18:24         ` Ihor Radchenko
2024-11-20 18:01           ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2024-10-08  2:58 Alexander Lazarević
2024-10-10  4:01 ` Alexander Lazarević

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='CAMPYxd=iUwLp0cKFNcrcABZ495eh0rziKeE3KjQmdwY6PWzfQg@mail.gmail.com' \
    --to=laza@e11bits.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).