Adam Porter

BTW, to be consistent with `:auto-planning` and with similar code in `org-ql`, there should be a `:planning` group selector that selects based on deadline or scheduled date, and the `:date`...

Not at all, we all do this in our free time. I'll leave this until I make the changes I mentioned, then we can decide what to do from there....

FYI, looking at PRs again, I'd like to tag a 1.2 release soon, so I'm going to mark this for the future.

No problem. It might be best to hold off on this feature until the package is updated to use `ts` for the timestamp-related selectors. On the other hand, I don't...

You could write a function to bind `org-super-agenda-groups` around a call to `org-agenda-list`.

You can see the implementation here: https://github.com/alphapapa/org-ql/blob/46f523d94a376b168176c75bbd0e3e0d00e61170/org-ql.el#L2218 The org-element `:priority` property is used, which comes from calling `org-element-headline-parser`. Maybe that function is not taking your manual priority values into account?

This is an interesting idea, yes. I'd generally recommend using `org-ql` as the base rather than `org-rifle`. See, e.g. * https://www.reddit.com/r/orgmode/comments/kdc4o2/getting_org_data_agendas_searchetc_from_the/ * https://github.com/alphapapa/org-ql/blob/master/examples/org-bills-due.el The hard parts, it seems to me,...

Sorry, I don't think this would be a good idea. It would make the searching code more complicated for little benefit. For abbreviations and expansions, there are several built-in packages...

Hi Matus, I think that would be more appropriate for Org Agenda skip functions rather than this package. That's more what they are designed for, AFAIK. But if that isn't...

This might be easier to implement now that `ts.el` is available, however I might need to add support for Org timestamp ranges to it.