From: Marcin Borkowski <mbork@mbork.pl>
To: Matt Lundin <mdl@imapmail.org>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Is there a way to get all agenda TODOs programmatically?
Date: Fri, 29 Dec 2017 20:55:32 +0100 [thread overview]
Message-ID: <877et5joln.fsf@mbork.pl> (raw)
In-Reply-To: <874lrasxu2.fsf@fastmail.fm>
On 2017-10-07, at 18:54, Matt Lundin <mdl@imapmail.org> wrote:
>>> Finally, if you want simply to gather the todo data programmatically for
>>> further processing you can use the function org-map-entries.
>>
>> Thanks, that seems to be a good pointer. I'll check it out.
>
> I think something like this would generate a such a list:
>
> (org-map-entries '(cons (nth 4 (org-heading-components))
> (list (org-get-deadline-time nil)))
> "/!TODO" 'agenda)
>
> Each item in the list would look something like this:
>
> ("Test" (23000 24400))
>
> You could then feed the list to whatever function you'd like.
Thanks again. I played around with this for some time, but there is one
problem. The agenda has a lot of settings, and replicating them with
org-map-entries turned out to be no fun.
Is there a way to plug into the agenda generating functions somehow to
get a Lisp list of agenda items? I'm pretty sure that can be done -
org-super-agenda does something similar, after all - but I have no idea
why. I could delve into agenda source myself, but is is quite hairy, so
maybe someone knows that already?
TIA,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-12-29 19:55 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 [this message]
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
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=877et5joln.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).