emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Duration Tally
Date: Mon, 18 Jun 2007 21:16:22 -0500	[thread overview]
Message-ID: <20070619021622.GA19944@odin.demosthenes.org> (raw)
In-Reply-To: <6c8fdacecb6dac733b1d8cd2987ddcb9@science.uva.nl>

I'm looking specificaly at project planning...

I like the idea of the key/value pairs under a heading, perhaps later
it could be used for other datatypes (TID,DEPENDS,ASSIGNED, etc).

I frequently use a tree of TODO's to describe steps in a project plan,
and check them off as they are completed. 


On Fri, Jun 15, 2007 at 08:21:22AM +0200, Carsten Dominik wrote:
> 
> On Jun 13, 2007, at 23:58, Scott Jaderholm wrote:
> 
> >On 6/13/07, Russell Adams <RLAdams@adamsinfoserv.com> wrote:
> >
> >>I'm planning ahead on some items, and having a way to represent the
> >>amount of time a TODO item will take
> >
> >On a similar note, I like using the clocktable to see how long things
> >have taken me, but sometimes I just want to put a time value under a
> >heading, not a time range (because I forgot to clock in/out). Could
> >CLOCK: => 2:00 or something similar work? If it did, maybe this could
> >work for Russell as well (if he didn't mind using a clocktable instead
> >of seeing it in the headline).
> 
> This one is definitely useful, so it is on the TODO list.
> 
> - Carsten
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

  reply	other threads:[~2007-06-19  2:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 13:47 Duration Tally Russell Adams
2007-06-13 15:33 ` Eddward DeVilla
2007-06-14  2:15   ` Russell Adams
2007-06-14 13:28   ` Jason F. McBrayer
2007-06-19  7:00   ` Carsten Dominik
2007-06-19 11:24     ` Russell Adams
2007-06-19 16:20     ` Eddward DeVilla
2007-06-19 17:45     ` Scott Jaderholm
2007-06-19 18:28       ` Eddward DeVilla
2007-06-22 15:56       ` Carsten Dominik
2007-06-22 19:06         ` Scott Jaderholm
2007-06-22 19:35           ` Eddward DeVilla
2007-06-13 21:58 ` Scott Jaderholm
     [not found]   ` <b71b18520706131837m42b32f5cs174d94c2b353d16d@mail.gmail.com>
2007-06-15  0:13     ` Fwd: " Eddward DeVilla
2007-06-15  6:21   ` Carsten Dominik
2007-06-19  2:16     ` Russell Adams [this message]
2007-06-19  7:02 ` Carsten Dominik
2007-06-19 11:21   ` Russell Adams
2007-06-19 13:10     ` Carsten Dominik
2007-06-19 17:12       ` Russell Adams

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=20070619021622.GA19944@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).