From: "Tom Davey" <firstname.lastname@example.org>
Subject: RE: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]
Date: Mon, 21 Mar 2022 11:58:16 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
> I personally see allowing timestamps (and links) inside property values as a useful feature.
> Would it be of interest for other users?
Yes, it's a quite useful feature. For years, via my Capture templates, I've been adding a property named :Created: to the properties drawer as follows:
:Created: <2022-03-06 Sun 22:42>
Now, in 9.5.2, literally hundreds of entries that formerly appeared on the built-in Agenda views cannot be easily found.
Regards to all,
PS The variable 'org-agenda-skip-additional-timestamps-same-entry seemed expressly made for my use case, to clean up same-day clutter in entries with a TODO timestamp.
New York NY USA
From: Emacs-orgmode <firstname.lastname@example.org> On Behalf Of Ihor Radchenko
Sent: Saturday, March 12, 2022 7:29 AM
To: Ignacio Casso <email@example.com>
Subject: Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]
Ignacio Casso <firstname.lastname@example.org> writes:
> In Emacs 27.2, with an up to date version of org from ELPA (9.5.2),
> org-agenda considers timestamps that appear in property drawers, so
> the entry below appears in the daily agenda view.
> * Heading
> :timestamp: <2022-03-12 sáb>
> However, in the latest Emacs version built from source (29.0.50), with
> the built-in version of org (also 9.5.2, but the latest release, I
> assume), this is no longer the case and that entry does not appear in
> the agenda view.
> I know that maybe it's unorthodox, but I have some org files that rely
> in the previous behavior, with entries like the following:
> * Some friend
> :birth-date: <1994-03-12 sáb +1y>
> Is this a bug? If it's not, can someone point me to the functions I
> need to touch to restore the previous behavior? Or maybe I should stop
> doing this and start moving those timestamps out of the properties
> drawer in my files?
What you see in the new Org version is not a bug. Property values are treated as plain text by Org.
In the older versions, agenda code did not rely on Org's internal parsing and matched timestamps in places where timestamps are not allowed (inside code blocks, for example). See https://orgmode.org/list/20220101122409.GA29829@itccanarias.org
I was unable to find a place in manual describing that timestamps cannot be placed inside property values:
>> A timestamp is a specification of a date (possibly with a time or a
>> range of times) in a special format, either ‘<2003-09-16 Tue>’ or
>> ‘<2003-09-16 Tue 09:39>’ or ‘<2003-09-16 Tue 12:00-12:30>’(1). A
>> timestamp can appear anywhere in the headline or body of an Org tree
>> entry. Its presence causes entries to be shown on specific dates in
>> the agenda (see *note Weekly/daily agenda::). We distinguish:
I personally see allowing timestamps (and links) inside property values as a useful feature. Would it be of interest for other users?
In any case, we should probably clarify manual in this regard.
next prev parent reply other threads:[~2022-03-21 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 10:06 Ignacio Casso
2022-03-12 12:28 ` Ihor Radchenko
2022-03-21 15:58 ` Tom Davey [this message]
2022-03-21 23:21 ` Ignacio Casso
2022-03-22 0:50 ` Samuel Wales
2022-03-22 10:02 ` Ihor Radchenko
2022-03-22 10:17 ` Ihor Radchenko
2022-03-22 21:02 ` Tim Cross
2022-03-23 12:07 ` Ihor Radchenko
2022-03-23 0:10 ` Samuel Wales
2022-03-23 12:21 ` Ihor Radchenko
2022-03-24 3:38 ` Samuel Wales
2022-03-22 3:43 ` Tom Davey
2022-03-22 9:47 ` Ihor Radchenko
2022-03-22 10:00 ` Timestamp parsing inside node properties and other contexts out of org-element-object-restrictions (was: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]) Ihor Radchenko
2022-03-22 21:10 ` Tim Cross
2022-03-22 23:16 ` Tom Davey
2022-03-23 0:25 ` Tim Cross
2022-03-23 13:13 ` Ihor Radchenko
2022-03-22 23:05 ` Timestamp parsing inside node properties and other contexts out of org-element-object-restrictions Nicolas Goaziou
2022-03-23 13:06 ` Ihor Radchenko
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 \
* 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).