From: Bastien <firstname.lastname@example.org>
To: "Peter Münster" <email@example.com>
Subject: Re: notify, when something to do
Date: Sun, 23 Oct 2011 23:29:19 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> ("Peter =?iso-8859-1?Q?M=FCnster=22's?= message of "Sun, 23 Oct 2011 20:17:57 +0200")
firstname.lastname@example.org (Peter Münster) writes:
> - I think, I'll need a filter for org-agenda-to-appt, because I only
> want TODO items. Should be no problem.
Yes -- just use a function who tries to match the TODO keyword
against the entry.
> - How to distinguish between SCHEDULED and DEADLINE? I'll
I introduced the ability to use
(org-agenda-to-appt nil t :scheduled)
if you just want to get scheduled appointments. This might
speeds things and make them more flexible.
> - Perhaps the main problem: appt does not know about warning periods.
> There are items with "-3d", other with "-5M". There is only one
> universal appt-message-warning-time. Would it be possible, to have a
> individual warning-time for each todo-item, directly computed from the
> warning time in the org-timestamp?
Check what info is available as text properties in the agenda
(with `C-u C-x =') and see if you can use this information in
a filter function.
next prev parent reply other threads:[~2011-10-23 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 10:07 notify, when something to do Peter Münster
2011-10-23 16:20 ` Tassilo Horn
2011-10-23 16:30 ` Tassilo Horn
2011-10-23 18:17 ` Peter Münster
2011-10-23 19:09 ` Tassilo Horn
2011-10-23 21:23 ` Bastien
2011-10-24 5:14 ` Tassilo Horn
2011-10-23 21:29 ` Bastien [this message]
2011-10-24 9:29 ` Sebastien Vauban
2011-11-01 23:01 ` Peter Münster
2011-10-24 15:01 ` Christopher Allan Webber
2011-10-25 18:56 ` Marcelo de Moraes Serpa
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).