From: Ihor Radchenko <yantar92@posteo.net>
To: Christian Barthel <bch@online.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Emacs 29.1, org-agenda and SCHEDULED entries
Date: Sat, 05 Aug 2023 11:18:07 +0000 [thread overview]
Message-ID: <875y5tlouo.fsf@localhost> (raw)
In-Reply-To: <87edkhnbn4.fsf@shell.onfire.org>
Christian Barthel <bch@online.de> writes:
> while upgrading from emacs 28.1 to 29.1, my org-agenda stopped working.
> The message in the echo area was:
>
> --8<---------------cut here---------------start------------->8---
> Search failed: "\\<SCHEDULED: *<\\([^>]+\\)>"
> --8<---------------cut here---------------end--------------->8---
>
> The search seemed to fail in an old org file:
>
> --8<---------------cut here---------------start------------->8---
> * someentry
> SCHEDULED: [2017-12-12 Tue 17:42]
> --8<---------------cut here---------------end--------------->8---
>
> Not sure why I've used an inactive timestamp there but it shouldn't
> be a problem I guess?
It is exactly the problem.
Inactive timestamps are not allowed in SCHEDULED/DEADLINE.
> Was/Is that change on purpose? (I haven't seen anything in the
> ChangeLog)
Only internals changed. Previously, agenda used a dumb regexp search
using this failing regexp (and skipped your problematic entry
completely). Now, we first query parser cache, which considers your
"someentry" as :scheduled. But agenda expects scheduled items to use
active timestamps all the time, causing the error.
We should update the parser to treat such malformed SCHEDULED/DEADLINE
lines as ordinary paragraphs and report them in org-lint.
--
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>
next prev parent reply other threads:[~2023-08-05 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 8:20 Emacs 29.1, org-agenda and SCHEDULED entries Christian Barthel
2023-08-05 11:18 ` Ihor Radchenko [this message]
2023-08-18 12:24 ` 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=875y5tlouo.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bch@online.de \
--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).