From: Trevor Murphy <email@example.com>
Subject: Can I ask "Which day is it?" when filtering org-agenda views?
Date: Tue, 10 Sep 2013 11:12:15 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
As preface, I'm aware that I may have gone too far down the rabbit
hole. I'm inserting many time grid lines (one per half hour)
into my agenda views so I have a visual sense of my free / busy
time. But I want time grid lines that have already passed to
disappear, freeing up screen real estate for later lines.
This was pretty easy. I customized `org-agenda-time-grid' to give
me a line at every half-hour interval. Then I set
`org-agenda-before-sorting-filter-function' to return nil for time
grid lines where the "time-of-day" text property is in the past.
In case that description isn't clear, I'm using (apologies for
(string= (nth 1 org-agenda-time-grid)
(get-text-property 0 'txt org-agenda-item))
(< (get-text-property 0 'time-of-day
(string-to-number (format-time-string "%H%M"))))
As an unanticipated side effect, my function also throws out time
grid lines when I view tomorrow (and other days) in the agenda
Is there an additional check I can throw into my function to only
filter if the "day" of the time grid line is today? I tried the
obvious (get-text-property 0 'day org-agenda-item) but it seems
that the "day" text property isn't put into the item until /after/
the filter-function gets a chance to process it.
Alternatively, if my attempted solution is brain-damaged please
let me know a better way to manage the time grid lines.
Trevor Murphy GnuPG Key: 0xCB06EAAF
next reply other threads:[~2013-09-10 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 15:12 Trevor Murphy [this message]
2013-09-11 1:19 ` Can I ask "Which day is it?" when filtering org-agenda views? Nick Dokos
2013-09-11 2:07 ` Trevor Murphy
2013-09-11 2:26 ` Jambunathan K
2013-09-11 2:27 ` Samuel Wales
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).