From: "Andrew J. Korty" <ajk@iu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans]
Date: Fri, 17 Sep 2010 08:48:38 -0400 [thread overview]
Message-ID: <46075.1284727718@iu.edu> (raw)
In-Reply-To: <87iq244kq6.fsf@fastmail.fm>
Matt Lundin <mdl@imapmail.org> wrote:
> --8<---------------cut here---------------start------------->8---
> * TODO Review really important document
> DEADLINE: <2010-10-31 Sun -2m>
> * TODO Review less important document
> DEADLINE: <2010-10-31 Sun>
> --8<---------------cut here---------------end--------------->8---
>
> Let's assume the following settings:
>
> --8<---------------cut here---------------start------------->8---
> (setq org-agenda-todo-ignore-deadlines 'far
> org-deadline-warning-days 14)
> --8<---------------cut here---------------end--------------->8---
>
> With these settings, the first task would show up *today* both in your
> agenda and in your TODO list, while the second task would appear in both
> places two weeks before the deadline.
Right, but what I want is for the second task to appear in the todo
list even before two weeks before the deadline, and I don't want it to
appear in the agenda until two weeks before the deadline. In other
words, I always want to see tasks I can do now in my todo lists,
whereas I only want to see tasks that are due soon in the agenda.
Lengthening the lead time won't help because it unnecessarily shows
tasks in the agenda that aren't due soon.
But maybe my usage is not an intended one.
ajk
next prev parent reply other threads:[~2010-09-17 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:01 Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans] Andrew J. Korty
2010-09-16 9:55 ` Bernt Hansen
2010-09-16 14:58 ` Andrew J. Korty
2010-09-16 15:28 ` Andrew J. Korty
2010-09-17 12:29 ` Matt Lundin
2010-09-17 12:48 ` Andrew J. Korty [this message]
2010-09-17 18:47 ` Matt Lundin
2010-09-17 21:34 ` Andrew J. Korty
2010-09-18 2:39 ` Matt Lundin
2010-09-18 13:08 ` Andrew J. Korty
2010-09-17 12:05 ` Matt Lundin
2010-09-17 12:43 ` Andrew J. Korty
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=46075.1284727718@iu.edu \
--to=ajk@iu.edu \
--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).