emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dennis J Lin <djlin@uiuc.edu>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: BUG?: repeat items disappears in agenda
Date: Sun, 20 Jan 2008 11:21:07 -0600	[thread overview]
Message-ID: <20080120172107.GK17250@seeker.homedns.org> (raw)
In-Reply-To: <48F709E7-8D83-4021-8AA1-4AB71A9ECE53@science.uva.nl>

Salutations!

> Hi Dennis, thanks for the patch.
>
> I am not sure yet if you are using the right condition though.  It seems to 
> me that extending the late-warning-period makes sens only for repeating 
> *tasks*, where the base date keeps changing each time you mark this entry 
> as DONE.  So maybe the condition should be that it is today *and* that the 
> item is a task marked by a TODO keyword.

Hmm, that may be -- every entry that has a date is a TODO for me.  I
would think that a non-todo entry (repeating or not) should only occur
on the day(s) where it's scheduled, since there is no way to mark it
"done" and get it off of today's agenda.

> Or: maybe for Scheduled, we should no relate to the *nearest* match of the 
> repeater, but to the most recent one.  This way you would get over-due 
> warnings right up to the day where the next occurrence of this item is 
> scheduled.  So you would never loose sight on the item.

However, if we do this, we lose information on *how* overdue a
particular item is.  I tend to keep things on the agenda and let the
large numbers shame me into getting things done...

Dennis Lin

      parent reply	other threads:[~2008-01-20 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 16:04 BUG?: repeat items disappears in agenda Wanrong Lin
2008-01-18 21:24 ` Dennis J Lin
2008-01-18 21:42   ` Carsten Dominik
2008-01-18 21:55     ` Dennis J Lin
2008-01-20 14:37       ` Carsten Dominik
2008-01-20 16:51         ` Bernt Hansen
2008-01-20 21:21           ` Wanrong Lin
2008-01-20 17:21         ` Dennis J Lin [this message]

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=20080120172107.GK17250@seeker.homedns.org \
    --to=djlin@uiuc.edu \
    --cc=dominik@science.uva.nl \
    --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).