From: Bernt Hansen <bernt@norang.ca>
To: Memnon Anon <gegendosenfleisch@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Organize Your Life In Plain Text!
Date: Thu, 07 May 2009 23:04:11 -0400 [thread overview]
Message-ID: <87vdocthw4.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87ljp88hvb.fsf@mean.albasani.net> (Memnon Anon's message of "Fri\, 8 May 2009 02\:10\:28 +0000 \(UTC\)")
Memnon Anon <gegendosenfleisch@gmail.com> writes:
> Okay, here is another question for all the clocking junkies out there ;).
>
> Is there a way to clock two items at the same time?
> This may sound stupid, 'who can do two things at the same time?'
> but please let me explain.
>
> Whoever clocks items, wants to keep control of what he/she does.
>
> If e.g. someone loves to listen to audio books and does this in several
> different contexts: Driving a car, at home etc. One could solve this by tags,
> e.g
>
> * Listening to audiobook
> ** ONGOING Listening to audiobook :car:
> ** ONGOING Listening to audiobook :home:
> ...
>
> and clock whatever may be right in each case.
>
> But, I guess, it would be easier/more flexible to clock items and locations
> seperately. I can have several items STARTED and SCHEDULED at the same
> time, but can I clock them at the same time?
>
> I am quite new to this 'clock your life' idea, so sorry if I am over
> enthusiastic ;).
Only one task can be clocked at a time using the standard org-mode
clocking functions. If you clock in a task any existing clocked task is
closed first.
ie. clock taskA, switch to taskB, clock in taskB (stops the clock for
taskA)
In your example above the clock times for the subtasks are totalled to
give the total time for the parent task when you do C-c C-x C-d or
generate a clock report.
HTH,
Bernt
next prev parent reply other threads:[~2009-05-08 3:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 16:49 Organize Your Life In Plain Text! Bernt Hansen
2009-05-07 18:22 ` Rick Moynihan
2009-05-07 18:44 ` Bernt Hansen
[not found] ` <4a035da6.0407560a.7391.ffffc270@mx.google.com>
2009-05-07 22:32 ` Bernt Hansen
2009-05-08 2:10 ` Memnon Anon
2009-05-08 3:04 ` Bernt Hansen [this message]
2009-05-07 22:50 ` Jonathan Arkell
2009-05-08 1:35 ` Rick Moynihan
2009-05-08 1:46 ` Eric Schulte
2009-05-08 14:08 ` Carsten Dominik
2009-05-08 15:32 ` Eric Schulte
2009-05-08 16:19 ` Carsten Dominik
2009-05-13 0:22 ` Rick Moynihan
2009-05-13 1:39 ` Bernt Hansen
2009-05-13 1:50 ` Bernt Hansen
2009-05-13 3:58 ` Carsten Dominik
2009-05-13 4:02 ` Bernt Hansen
2009-05-13 10:04 ` Sebastian Rose
2009-05-13 10:15 ` Rick Moynihan
2009-05-14 13:33 ` Eric Schulte
2009-05-14 19:30 ` Sebastian Rose
2009-05-14 19:55 ` Keith Lancaster
2009-05-14 22:16 ` Eric Schulte
2009-05-15 6:54 ` Ian Barton
2009-05-15 22:18 ` Eric Schulte
2009-05-16 6:56 ` Ian Barton
2009-05-17 21:49 ` Eric Schulte
2009-05-18 6:06 ` Ian Barton
2009-05-18 13:17 ` Eric Schulte
2009-05-19 9:19 ` Ian Barton
2009-05-14 11:36 ` Carsten Dominik
2009-05-14 19:11 ` 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=87vdocthw4.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=gegendosenfleisch@gmail.com \
/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).