From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: FR: multiple scheduling of one item?
Date: Mon, 31 Dec 2007 15:21:58 +0000 [thread overview]
Message-ID: <20071231152158.GN20947@atlantic.linksys.moosehall> (raw)
Imagine I have a single project or task which I know will require
several sessions to complete. Before I get to the stage of analysing
it closely and breaking it down into sub-tasks, it would be good to
reserve some diary time in advance, so that I don't accidentally
accept other commitments for that time and overstretch myself.
However, this is different from booking a normal diary appointment, in
the sense that I am not making a commitment to other people to be in a
particular place at a particular time: the commitment is only to
myself and is directly associated with a particular project or task.
Therefore it sounds like it would be useful to be able to schedule the
same task for multiple slots. It turns out that the org-agenda code
already handles this beautifully; if you do:
* Long task/project not yet broken down into sub-tasks
SCHEDULED: <2008-01-07 Mon>
SCHEDULED: <2008-01-08 Tue>
and it appears in both places in an agenda view, and you can jump back
to the item in the normal way. The only downside is that C-c C-s
doesn't currently support entering it:
(org-schedule &optional REMOVE)
Insert the SCHEDULED: string with a timestamp to schedule a TODO item.
With argument REMOVE, remove any scheduling date from the item.
How about doing the usual trick of comparing different prefix argument
values (e.g. 4 vs. 16) to allow adding a new scheduled slot?
next reply other threads:[~2007-12-31 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 15:21 Adam Spiers [this message]
2008-01-03 7:44 ` FR: multiple scheduling of one item? Carsten Dominik
2008-01-03 12:51 ` Adam Spiers
2008-01-03 22:39 ` Giovanni Ridolfi
2008-01-04 9:55 ` Adam Spiers
2008-01-07 2:52 ` Bastien
2008-01-07 10:14 ` Adam Spiers
2008-01-07 10:34 ` Bastien
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=20071231152158.GN20947@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--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).