From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten@orgmode.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Agenda clock report - adding new columns
Date: Thu, 16 Apr 2009 13:02:03 -0400 [thread overview]
Message-ID: <878wm0y1kk.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87d4bcy5bq.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Thu\, 16 Apr 2009 11\:40\:57 -0400")
(replying to my own post)
Bernt Hansen <bernt@norang.ca> writes:
> I know other people (including you) have limits on the amount of time
> they spend on a task in a day but I haven't really found a good working
> solution for this yet that fits my needs. For a single task this is
> easy but I'd like to not have to remember the limits for multiple tasks
> -- that's what I use org for ;) to get all these details out of my head.
>
> Is something like this doable? Does anyone have a better idea for how
> to deal with this?
Maybe I'm over-engineering this... Just putting the limit in the
headline text works for me...
I just added [MAX xxx] and [MIN yyy] to my headline and that'll work.
It's probably not a pretty as a property could be but it's _lots_ less
work to implement :)
| File | L | Headline | Time | | |
|------------+---+---------------------------------------------------------------------------+--------+------+------|
| org.org | | *File time* | *0:15* | | |
| org.org | 1 | Documentation | 0:15 | | |
| org.org | 2 | STARTED Writeup on my use of org-mode [MAX 1h] | | 0:15 | |
|------------+---+---------------------------------------------------------------------------+--------+------+------|
-Bernt
next prev parent reply other threads:[~2009-04-16 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 15:40 Agenda clock report - adding new columns Bernt Hansen
2009-04-16 17:02 ` Bernt Hansen [this message]
2009-04-16 17:14 ` David Bremner
2009-04-16 18:05 ` Bernt Hansen
2009-04-16 20:31 ` Carsten Dominik
2009-04-16 20:55 ` Bernt Hansen
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=878wm0y1kk.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten@orgmode.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).