-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for timestamps with internal time ranges (events) #371
Comments
This is a nicely written bug report, but please see #237, which it duplicates. |
I must have only searched issues. Well, now there is an issue that PR can close 😅 |
Yeah, probably good to have this as an issue, and since you wrote it up so well, might as well use this one. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Org QL does not currently match timestamps with internal time ranges, commonly used for events. These are different from time/date ranges where two timestamps are connected by
--
.The example from the manual:
Interestingly, the latest Org Syntax document just defines times as:
I was wondering if the Org QL behavior was by design or simply because you don’t personally use these. I think this could be fixed by changing the timestamp regexp, but the predicate code is pretty complex, so I don’t know the full implications of that.
Somewhat related to #159
Matching these timestamps would be another step towards fully replacing the Org agenda with Org QL (and its caching!). There is currently no mechanism for generating an Org agenda-like time grid, but I think it makes sense for Org QL to limit its scope to simply returning (and in the case of
org-ql-view
, displaying) lists of headings. Matching timestamps with internal time ranges would mean a package likecalfw
could leverage acalfw-org-ql
backend rather than theorg-agenda
-basedcalfw-org
.The text was updated successfully, but these errors were encountered: