Closed swflint closed 3 years ago
Could you give an example of what problem this solves?
I frequently have as headlines:
** <2020-12-02 Wed 12:00> Event
By default, the whole headline is shown, timestamp included. My headlines can get fairly long (due to inclusion of things like Zoom details, etc), and the inclusion of the timestamp can prevent that from being shown (particularly if I'm using my laptop).
from what I can tell, this requires the timestamp to be on the headline? I typically use this format
** meet
<2020-12-02 on. 12:00>
which doesn't seem to be parsed by this
Interesting. I'll see what IÂ can do with that.
btw https://github.com/unhammer/org-upcoming-modeline/tree/org-element-map was my attempt at rebasing if you want to work off the newest – note that the org-ql selector now uses (ts-now)
so shouldn't need to check that timestamps are >=now outside the loop (we were doing ts-active :from 0
which ql turns into (ts-adjust :hour 0 minute 0 (ts-now))
)
Superseded by #8
This also a) de-propertizes the strings, b) cleanly handles "scheduled" items, and c) does everything in one fell swoop.
Note, if you use this, #4 is unnecessary. This would likely be more helpful.