From: James Harkins <jamshark70@qq.com>
To: emacs-orgmode@gnu.org
Subject: Sharing: Agenda skip function to remove future-scheduled items
Date: Tue, 14 Oct 2014 12:43:48 +0800 [thread overview]
Message-ID: <87egubjm63.wl-jamshark70@qq.com> (raw)
I often ask questions, or complain about things (or both at the same time), so it's nice to share something.
I was making a block agenda, splitting up tasks by location (loosely inspired by GTD). But I realized that I didn't want to see items that are scheduled for the future, because this is my agenda view for "what tasks are available right now." For example, if I have a task to update my grade sheet, it doesn't make sense to do that before I've taught the lessons -- so I don't want to see the task until it's actually due.
I didn't find a straightforward way to use a property search such as "scheduled is nil or scheduled > today," but I did (with some false starts) hack up a skip function that seems to do the job. So, in the relevant blocks, I have (org-agenda-skip-function 'hjh-skip-future-scheduled), and... perfect.
(I'm sure it's not the most efficient, but I found elisp's time comparisons to be confusing, and I didn't want to consider time-of-day either. Performance is OK for my use.)
hjh
; agenda skip function to remove items scheduled for a future date
(defun hjh-skip-future-scheduled ()
"Skip trees that are scheduled in the future"
(let* ((subtree-end (save-excursion (org-end-of-subtree t)))
(schedprop (cdr (assoc "SCHEDULED" (org-entry-properties))))
(schedymd (if(stringp schedprop) (substring schedprop 0 10))))
(if schedymd
(if (string< (format-time-string "%Y-%m-%d" (current-time)) schedymd) subtree-end nil)
nil)))
next reply other threads:[~2014-10-14 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 4:43 James Harkins [this message]
2014-10-14 12:38 ` Sharing: Agenda skip function to remove future-scheduled items Sebastien Vauban
2014-10-15 2:42 ` James Harkins
2014-10-16 7:53 ` Sebastien Vauban
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=87egubjm63.wl-jamshark70@qq.com \
--to=jamshark70@qq.com \
--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).