jiri/org-ql
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Tidy: (org-ql--pre-process-query) Calling of --query-predicate

Browse source
This commit is contained in:
Adam Porter 2020-01-22 22:56:04 -06:00
parent 0e1196fd6f
commit 18c6787244
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
org-ql.el
View file

@ -549,9 +549,9 @@ Replaces bare strings with (regexp) selectors, and appropriate
(`(descendants ,query) `(descendants ',query)) (`(descendants ,query) `(descendants ',query))
(`(descendants) '(descendants (lambda () t))) (`(descendants) '(descendants (lambda () t)))
(`(parent ,query) `(parent ,(org-ql--query-predicate (rec query)))) (`(parent ,query) `(parent ,(org-ql--query-predicate (rec query))))
(`(parent) `(parent ,(org-ql--query-predicate (rec '(lambda () t))))) (`(parent) '(parent (lambda () t)))
(`(ancestors ,query) `(ancestors ,(org-ql--query-predicate (rec query)))) (`(ancestors ,query) `(ancestors ,(org-ql--query-predicate (rec query))))
(`(ancestors) `(ancestors ,(org-ql--query-predicate (rec '(lambda () t))))) (`(ancestors) '(ancestors (lambda () t)))
;; Timestamp-based predicates. I think this is the way that makes the most sense: ;; Timestamp-based predicates. I think this is the way that makes the most sense:
;; set the limit to N days in the future, adjusted to 23:59:59 (since Org doesn't ;; set the limit to N days in the future, adjusted to 23:59:59 (since Org doesn't
;; support timestamps down to the second, anyway, there should be no need to adjust ;; support timestamps down to the second, anyway, there should be no need to adjust