this is merely intuition, but i can - understand why planning line tses should not be matched in various places; they are closely tied to real org entries - not quite grasp why bare active and inactive tses should not be matched by ts agenda almost anywhere including blocks. perhaps the idea is that you might wnt to store lots of data with tses and they would be too much clutter? - understand that there are probably plenty of implementation issues that might obtrude and should be respected
so i guess i am interested in the rationale. example of ts [and text] search being useful might be an example or ledger block that contains ledger source, or something like that. i can get why bare ts not being matched inside links might be useful. otoh i can get why text [not ts] and isearch search inside of links can be useful. idk if my intuitions match those of others. i am partly trying to think of what a newcomer might expect to work [and the simplicity of a rule that he or she would have to remember in order to know what the behavior will be]. On 3/21/22, Ignacio Casso <ignacioca...@hotmail.com> wrote: > >>> What you see in the new Org version is not a bug. Property values are >>> treated as plain text by Org. >>> >>> I was unable to find a place in manual describing that timestamps cannot >>> be placed inside property values: > >>> 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: >> >> :PROPERTIES: >> :Created: <2022-03-06 Sun 22:42> >> :END: >> >> Now, in 9.5.2, literally hundreds of entries that formerly appeared on the >> built-in Agenda views cannot be easily found. > > > It seems that I'm not the only one using this unintended feature in > previous versions of org, and probably there will be many others who > don't use the latest version of org and have not noticed yet but will > have the same problem when they upgrade. > > I think that even if timestamps were never intended to be used inside > property drawers before, the fact that it worked for a long time and > nothing in the documentation suggested otherwise makes it a de facto > feature, even if unintended, and should be preserved. > > I've located the line in org-agenda.el responsible of the new behavior, > and the following patch seems to fix it. I suggest it is incorporated > into the repository, maybe with a variable > org-agenda-skip-timestamps-in-properties-drawer defaulting to t if not > everyone agrees. > > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
