From: Austin Frank <austin.frank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: GOAL keyword with DEADLINE semantics?
Date: Tue, 10 Mar 2009 03:15:59 -0400 [thread overview]
Message-ID: <m03adlyhjk.fsf@gmail.com> (raw)
In-Reply-To: 45FD3D92-E16C-477C-BBF7-7BF00DF4E479@uva.nl
[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]
On Mon, Mar 09 2009, Carsten Dominik wrote:
> since you want to use the same semantics as for deadlines, i.e. the
> same warning period etc, this really is a psychological issue :-)
But isn't that why we have org-mode in the first place-- to help us
label our way out of these pesky psychological issues? :P
> What I would do if I was bothered by this would be
>
> (setq org-deadline-string "DUE:")
>
> which captures both the colors of DEADLINE and GOAL pretty well, I
> think.
Yes, I will use this.
I think that the case I described where I wanted both a GOAL and a
DEADLINE for the same task can be handled reasonably well by creating
two different tasks and giving each a due date. So instead of
* TODO submit manuscript
GOAL: <optimistic date>
DEADLINE: <hard deadline>
I can do
* TODO submit manuscript
DUE: <optimistic date>
*** publisher deadline
DUE: <hard deadline>
This way I have all of the information in one place, and both dates get
into the agenda. The top level TODO and its due date represent my goal
for submitting. The sub-heading isn't a TODO because I'm working on my
schedule, not theirs. But, I put the hard deadline there just in case
my schedule and the official deadline get too close for comfort. Also,
if I keep them close together, then follow mode helps me see both at the
same time.
I don't know if DEADLINE timestamps are supposed to be applied to
non-TODO headings, but it didn't seem to break anything, so I'm going to
go forward with this approach for now.
Thanks,
/au
--
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
[-- Attachment #1.2: Type: application/pgp-signature, Size: 193 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2009-03-10 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 15:36 GOAL keyword with DEADLINE semantics? Austin Frank
2009-03-08 22:54 ` Shelagh Manton
2009-03-09 12:01 ` Carsten Dominik
2009-03-09 14:35 ` Bernt Hansen
2009-03-10 17:52 ` Carsten Dominik
2009-03-10 7:15 ` Austin Frank [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=m03adlyhjk.fsf@gmail.com \
--to=austin.frank@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).