From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: depending TODOs, scheduling following TODOs automatically
Date: Mon, 8 Oct 2007 15:12:23 -0500 [thread overview]
Message-ID: <20071008201223.GC10774@odin.demosthenes.org> (raw)
In-Reply-To: <4451bef76a71d49ffc88d9d8b87f2940@science.uva.nl>
On Mon, Oct 08, 2007 at 09:48:28PM +0200, Carsten Dominik wrote:
>
> On Oct 8, 2007, at 15:52, Russell Adams wrote:
>
> >I know I'm replying to myself, but I had an idea.
> >
> >If a link could show the state of a linked TODO, that would make for a
> >good visualization. I could then follow the link and just adjust my
> >order to account for dependencies. It sounds like a more "permanent"
> >agenda view that you could edit to get the right order.
> >
> >Ie:
> >
> >* Things to do in reverse order
> >** TODO One
> >** TODO Two
> >** TODO Three
> >
> >* Implementation Order
> >
> > TODO Three
> > TODO Two
> > TODO One
>
> I don't know what others think, but I did not understand a single word
> of this message :-) Could you please be a bit more verbose?
>
> - Carsten
I don't use links often... If I could have a link to another TODO
item, but have the visible portion of the link display the status of
the target TODO item.
Ie:
* Things to do in reverse order
** TODO One
** TODO Two
** DONE Three
* Implementation Order
[[file:..*Three][DONE Three]]
[[file:..*Two][TODO Two]]
[[file:..*One][TODO One]]
This way I can follow the link from the implementation order to the
right todo item, the part that is missing is an automated state update
regarding the TODO linked to.
Better? ;]
Russell
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2007-10-08 20:12 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 6:56 depending TODOs, scheduling following TODOs automatically Rainer Stengele
2007-10-08 13:26 ` Denis Bueno
2007-10-08 13:43 ` Russell Adams
2007-10-08 13:52 ` Russell Adams
2007-10-08 19:48 ` Carsten Dominik
2007-10-08 20:12 ` Russell Adams [this message]
2007-10-09 10:13 ` Carsten Dominik
2007-10-08 14:49 ` Eddward DeVilla
2007-10-08 20:55 ` Bastien
2007-10-08 20:26 ` Adam Spiers
2007-10-09 2:15 ` Bastien
2007-10-09 3:03 ` John Wiegley
2007-10-09 3:47 ` Eddward DeVilla
2007-10-09 9:27 ` Richard G Riley
2007-10-09 14:39 ` Eddward DeVilla
2007-10-10 17:20 ` Bastien
2007-10-09 10:35 ` Bastien
2007-10-09 10:32 ` Bastien
2007-10-11 14:46 ` Carsten Dominik
2007-10-11 15:53 ` pete phillips
2007-10-11 16:22 ` Sebastjan Trepca
2007-10-11 16:37 ` Russell Adams
2007-10-11 17:10 ` pete phillips
2007-10-11 17:55 ` Russell Adams
2007-10-11 18:45 ` pete phillips
2007-10-14 1:01 ` Charles Cave
2007-10-14 2:42 ` Bastien
2007-10-11 19:46 ` Bastien
2007-10-11 21:12 ` Rainer Stengele
2007-10-11 21:19 ` Leo
2007-10-11 23:54 ` Piotr Zielinski
2007-10-12 3:14 ` Eddward DeVilla
2007-10-12 13:50 ` Bastien
2007-10-12 17:09 ` Jason F. McBrayer
2007-10-12 17:03 ` Jason F. McBrayer
2007-10-11 16:53 ` Bastien
2007-10-12 9:21 ` John Wiegley
2007-10-08 20:35 ` Eddward DeVilla
2007-10-09 2:42 ` Bastien
2007-10-09 2:01 ` Russell Adams
2007-10-09 3:35 ` Eddward DeVilla
2007-10-09 3:59 ` Russell Adams
2007-10-09 4:55 ` Eddward DeVilla
2007-10-09 10:42 ` Bastien
2007-10-09 3:37 ` Bastien
2007-10-09 2:58 ` Eddward DeVilla
2007-10-09 10:41 ` Bastien
2007-10-09 14:53 ` Eddward DeVilla
2007-10-11 12:44 ` Bastien
2007-10-11 12:22 ` Russell Adams
2007-10-11 14:03 ` Bastien
2007-10-11 13:21 ` Russell Adams
2007-10-11 13:31 ` Eddward DeVilla
2007-10-12 9:13 ` John Wiegley
2007-10-09 9:44 ` Christian Egli
2007-10-09 10:53 ` Bastien
2007-10-09 15:21 ` Eddward DeVilla
2007-10-11 12:44 ` 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=20071008201223.GC10774@odin.demosthenes.org \
--to=rladams@adamsinfoserv.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).