From: SW <sabrewolfy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: if both schedule and deadline, appear only once in agenda
Date: Wed, 30 May 2012 09:12:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20120530T110720-856@post.gmane.org> (raw)
In-Reply-To: 87lka88nf9.fsf@bzg.ath.cx
I know I'm bumping a thread from 5 years ago :)
Bastien <bzg <at> altern.org> writes:
> Gijs Hillenius <gijs <at> hillenius.net> writes:
>
> > But maybe I should not . But here goes: I plan to start working on
> > an item by date X -> schedule stamp. The item has a deadline, so ->
> > deadline.
>
> For that I use `org-deadline-warning-days'. I start the deadline when
> it shows up in my agenda. The default value for this is 14, but you can
> set a value for each deadline like this:
>
> DEADLINE: <2004-02-29 Sun -10d>
>
> Meaning that you should start the deadline 10 days before the deadline.
>
> ,----[ (info "(org)Deadlines and scheduling") ]
> | You can specify a different lead time for warnings for a specific
> | deadlines using the following syntax. Here is an example with a
> | warning period of 5 days `DEADLINE: <2004-02-29 Sun -5d>'.
> `----
I think what the OP wanted (and what lead me to this thread) is an advanced
warning for *scheduled* items. For example, I'd like to know on the Friday
before that I have a scheduled item starting on the Monday. To do this I
SCHEDULE the item to Monday and then also set a DEADLINE for Monday, which will
obviously warn be in advance. I'm not unhappy with this solution, but I was
wondering if there were an alternative.
next prev parent reply other threads:[~2012-05-30 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 5:28 if both schedule and deadline, appear only once in agenda Gijs Hillenius
2007-10-12 13:05 ` Bastien
2007-10-12 12:21 ` Gijs Hillenius
2007-10-12 13:36 ` Bastien
2012-01-10 10:15 ` Detlef Steuer
2012-05-30 9:12 ` SW [this message]
2012-05-30 9:46 ` suvayu ali
2012-05-30 9:52 ` SW
2012-06-01 8:09 ` Eric S Fraga
2012-06-05 22:31 ` Mike McLean
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=loom.20120530T110720-856@post.gmane.org \
--to=sabrewolfy@gmail.com \
--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).