emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: Olaf Dietsche <olaf+list.orgmode@olafdietsche.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Journal versus clock tables: Opposing requirements?
Date: Mon, 7 Nov 2011 14:51:59 +0000	[thread overview]
Message-ID: <CAMg28Ot=Ti+6-gSFj6qT48d4ZT=E3shXDiD-BCavnZv4jf8X8w@mail.gmail.com> (raw)
In-Reply-To: <87obwogo1c.fsf@rat.lan>

Olaf wrote:
> Maybe I misunderstand what you want to accomplish, but if you put your
> journal into a separate file (e.g. journal.org), ...

That's pretty much what I want. But if I do that I then have trouble
with getting sensible clock tables. For example, suppose I had:

*** Headline about some activity on Project A
CLOCK: [from]--[to] => duration
notes notes notes

*** Headline about some activity on Project B
CLOCK: [from]--[to] => duration
more notes notes note

*** Headline about some other activity on Project A
CLOCK: [from]--[to] => duration
yet more notes notes

Adding those as a chronological journal lets me get a report of
chronology, but it won't let me have a clock table with the times for
the two "on Project A" activities combined into one. Will it?

Of course I could shove the Project A activities under one single
higher-level headline, but that than violates the chronology side of
things (in the sense that I want to enter things into my journal in
chronological order, just as I would in a paper log book).

> You can create clock tables and select reported items by tags. So, if
> you tag your journal entries, you can create clock tables made up of a
> few entries only.

OK, that might be what I need then. I thought clock tables grouped
things by headings, not by tags. I'll have a look at the manual.

thanks,
Tommy

  reply	other threads:[~2011-11-07 14:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  8:31 Journal versus clock tables: Opposing requirements? Tommy Kelly
2011-11-07 11:27 ` Bernt Hansen
2011-11-07 14:55   ` Tommy Kelly
2011-11-08  3:21     ` Bernt Hansen
2011-11-08  8:06       ` Tommy Kelly
2011-11-08  8:23         ` Carsten Dominik
2011-11-08 12:28         ` Bernt Hansen
2011-11-08 17:07         ` Bernt Hansen
2011-11-07 11:38 ` Olaf Dietsche
2011-11-07 14:51   ` Tommy Kelly [this message]
2011-11-07 17:19     ` Tommy Kelly
2011-11-08  9:04       ` Olaf Dietsche
2011-11-08  9:54         ` Carsten Dominik
2011-11-08  9:55         ` Tommy Kelly
2011-11-08 10:00           ` Carsten Dominik
2011-11-08 10:05             ` Sebastien Vauban
2011-11-08 10:15               ` Carsten Dominik
2011-11-08 10:33                 ` Sebastien Vauban
2011-11-08 10:41                 ` Tommy Kelly
2011-11-24 14:57         ` Eric S Fraga
2011-11-24 22:01           ` Olaf Dietsche

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='CAMg28Ot=Ti+6-gSFj6qT48d4ZT=E3shXDiD-BCavnZv4jf8X8w@mail.gmail.com' \
    --to=tommy.kelly@verilab.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=olaf+list.orgmode@olafdietsche.de \
    /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).