You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIU, internally in Org, every entry has a priority, because the default priority is equivalent to priority B. (I don't like that, myself, so some of my code in org-super-agenda and org-ql treats entries without explicit priorities as not having one.)
alphapapa
changed the title
Is ":priority nil" a valid selector option?
Allow (:priority nil) to match entries without explicit priorities
Mar 26, 2022
I ran into this recently, here's a quick solution with :pred:
(:name"Tasks Lacking Priority":and (:todo"TODO":not (:pred (lambda (s)
(string-match org-priority-regexp s)))))
I tried using regexp directly with (:regexp org-priority-regexp) but kept running into errors of the type Wrong type argument: sequencep, ... despite trying a few different ways to pass the variable in. I'm sure it's possible somehow but the :pred option got the job done and I moved on.
I would like to group items without an assigned priority, but
:priority nil
doesn't seem to work select those items.Would you please confirm whether
:priority nil
is a valid selector option?I haven't tried yet, but I think the nil grouping can still be achieved using something like:
:not (:priority>= "F")
(#F is my lowest priority).I'm just asking in case it is an error on my part.
Thanks!
The text was updated successfully, but these errors were encountered: