From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Is there a way to get all agenda TODOs programmatically?
Date: Wed, 03 Jan 2018 08:19:13 -0600 [thread overview]
Message-ID: <87h8s3t47y.fsf@alphapapa.net> (raw)
In-Reply-To: 87po6rt76o.fsf@alphapapa.net
Forgive the self reply, but I just made a change which makes the code
much more pleasant. The matching functions are bound internally during
matching, so instead of:
(org-agenda-ng--agenda
:files org-agenda-files
:pred (lambda ()
(and (org-agenda-ng--todo-p)
(or (org-agenda-ng--date-p :deadline '<= (org-today))
(org-agenda-ng--date-p :scheduled '<= (org-today)))
(not (apply #'org-agenda-ng--todo-p org-done-keywords-for-agenda)))))
You can write:
(org-agenda-ng--agenda
:files org-agenda-files
:pred (lambda ()
(and (todo)
(or (date :deadline '<= (org-today))
(date :scheduled '<= (org-today)))
(not (apply #'todo org-done-keywords-for-agenda)))))
Or:
(org-agenda-ng--agenda
:files org-agenda-files
:any `((date :date <= ,(org-today))
(date :deadline <= ,(+ org-deadline-warning-days (org-today)))
(date :scheduled <= ,(org-today)))
:none `((apply todo ,org-done-keywords)))
This makes the syntax much more pleasant and readable, I think. I also
profiled the code, and its performance seems good.
next prev parent reply other threads:[~2018-01-03 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 4:43 Is there a way to get all agenda TODOs programmatically? Marcin Borkowski
2017-10-07 14:20 ` Matt Lundin
2017-10-07 16:43 ` Marcin Borkowski
2017-10-07 16:54 ` Matt Lundin
2017-12-29 19:55 ` Marcin Borkowski
2017-12-31 23:37 ` Adam Porter
2018-01-03 9:31 ` Marcin Borkowski
2018-01-03 9:50 ` Adam Porter
2018-01-03 13:15 ` Adam Porter
2018-01-03 14:15 ` Nicolas Goaziou
2018-01-03 15:48 ` Adam Porter
2018-01-03 14:19 ` Adam Porter [this message]
2018-01-03 13:49 ` Nicolas Goaziou
2018-01-03 14:16 ` Adam Porter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8s3t47y.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).