From: Christian Egli <christian.egli@novell.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org, Dieter Grollmann <groll-ay@bluewin.ch>
Subject: Re: Re: Cyclic timestamps for SCHEDULED and DEADLINE
Date: Fri, 28 Apr 2006 18:23:53 +0200 [thread overview]
Message-ID: <1146241433.3697.14.camel@elrond.zur.novell.com> (raw)
In-Reply-To: <c45ab1bd54661ebae73816f14bd238fe@science.uva.nl>
Hi
On Fri, 2006-04-28 at 09:07 +0200, Carsten Dominik wrote:
> > So automatic scheduling or deadlining for cyclic tasks which
> > would insist on being displayed as TODO until I mark them as DONE
> > could be helpful for me in such times.
>
> Yes I understand. A very basic problem with cyclic scheduling is that
> if you don't mark the entry DONE, then you can get many of those tasks
> in your agenda.
But AFAIK this is only a problem because the scheduled tasks show up in
the "all currently open items" section. If scheduled items would no
longer show up there then this problem would not exist, wouldn't it?
> One simple way would be to create a separate file and just put those
> cyclic tasks for the next two years in there.
Couldn't this be done with the calendar integration of org? Ah, now that
I checked the documentation I see that I can only get dates
(anniversaries, etc) from calendar, but not TODO items. I guess a
mechanism for periodic TODO items would have to come from org-mode as
diary only knows about (periodic) events but has no concept of periodic
TODO items.
Christian
next prev parent reply other threads:[~2006-04-29 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:42 Cyclic timestamps for SCHEDULED and DEADLINE Dieter Grollmann
2006-04-27 7:16 ` Carsten Dominik
2006-04-28 0:33 ` Dieter Grollmann
2006-04-28 7:07 ` Carsten Dominik
2006-04-28 14:37 ` Dieter Grollmann
2006-04-28 16:23 ` Christian Egli [this message]
2006-05-06 4:01 ` Carsten Dominik
2006-05-02 3:07 ` Dan Christensen
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=1146241433.3697.14.camel@elrond.zur.novell.com \
--to=christian.egli@novell.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=groll-ay@bluewin.ch \
/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).