emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <zthjwsqqafhv-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Clocking work time with a date not a time only
Date: Thu, 02 Apr 2009 10:55:43 +0200	[thread overview]
Message-ID: <878wmjph80.fsf@mundaneum.com> (raw)
In-Reply-To: <155496.90395.qm-+muOpk2Ss/nGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org> (Giovanni Ridolfi's message of "Wed, 1 Apr 2009 13:56:42 +0000 (GMT)")

Hi Giovanni and Jan,

>> I use Clocking work time function for a logging my work. [...] I would like
>> have in a table not a times but a dates too.

I have related questions on this subject as well...

Up to now, I was clocking time with timeclock-x under Emacs, and files such
as:

--8<---------------cut here---------------start------------->8---
i 2009/02/02 08:45:00 Client1
o 2009/02/02 09:35:00


>> Reading my mails.
i 2009/02/02 09:35:00 Client2
o 2009/02/02 12:30:00


>> Analysing their stuff for CCh.
i 2009/02/02 13:35:00 Client1
o 2009/02/02 17:30:00


>> Written the big report.
--8<---------------cut here---------------end--------------->8---

This is nice because it is chronological and I have notes about every clocked
time, but that's all...

Org beats this by orders of magnitude. That's why I've decided to begin now to
use Org as well for that.

Here is my example for these first 2 days of April:

--8<---------------cut here---------------start------------->8---

* 2009-04

*** Client1
    :LOGBOOK:
    CLOCK: [2009-04-01 Wed 09:05]--[2009-04-01 Wed 12:00] =>  2:55
    CLOCK: [2009-04-01 Wed 13:10]--[2009-04-01 Wed 16:30] =>  3:20
    CLOCK: [2009-04-02 Thu 08:55]
    :END:

*** Client2
    :LOGBOOK:
    CLOCK: [2009-04-01 Wed 12:00]--[2009-04-01 Wed 12:30] =>  0:30
    CLOCK: [2009-04-01 Wed 16:30]--[2009-04-01 Wed 17:15] =>  0:45
    :END:


#+BEGIN: clocktable :maxlevel 2 :scope file :block today
Clock summary at [2009-04-02 Thu 10:41], for Thursday, April 02, 2009.

| L | Headline     | Time   |
|---+--------------+--------|
|   | *Total time* | *0:00* |
|---+--------------+--------|
#+END:


#+BEGIN: clocktable :maxlevel 2 :scope file
Clock summary at [2009-04-02 Thu 10:41]

| L | Headline     | Time   |      |
|---+--------------+--------+------|
|   | *Total time* | *7:30* |      |
|---+--------------+--------+------|
| 1 | 2009-04      | 7:30   |      |
| 2 | Client1      |        | 6:15 |
| 2 | Client2      |        | 1:15 |
#+END:

--8<---------------cut here---------------end--------------->8---

Fantastic is that I can check how much time I've globally worked on which
project for this day and for this month at the same time.

Though:

- how can I associate a one-line comment to every block of time that I clock?
  The goal is to be able to justify, later, what I did on the different days I
  worked for them (and put that in their bill).

  Am I forced to add sub-headlines for every block of time?  Is there another
  better (clearer) way to do?

- is there a possibility to get back, out of such a file, a chronological view
  of the whole file (where all projects are mixed)?

Once again, and mainly to Carsten, thanks a lot^100 for the great work you've
done and shared... This is one fantastic way to lock me more in Emacs, which
is something I love.

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2009-04-02  8:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 13:56 Clocking work time with a date not a time only Giovanni Ridolfi
     [not found] ` <155496.90395.qm-+muOpk2Ss/nGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2009-04-02  8:55   ` Sébastien Vauban [this message]
2009-04-02  9:37     ` Carsten Dominik
     [not found]       ` <AAD9B813-70C7-4F6E-8053-A642F3C7FD65-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-02 12:08         ` Sébastien Vauban
2009-04-02 14:01           ` Carsten Dominik
2009-04-02 14:11             ` Carsten Dominik
     [not found]               ` <DC748614-4A82-44BE-A891-DC919ECF8264-V/Xpf/srekw@public.gmane.org>
2009-04-02 14:49                 ` Sébastien Vauban
2009-04-02 16:23                   ` Carsten Dominik
2009-04-03  8:49                   ` Carsten Dominik
2009-04-03 10:20                     ` Jan Buchal
2009-04-03 10:32                       ` Carsten Dominik
2009-04-03 11:58                     ` Sébastien Vauban
     [not found]                       ` <87myayc5jn.fsf-pwAqS3aGAJQybS5Ee8rs3A@public.gmane.org>
2009-04-03 12:10                         ` Sébastien Vauban
2009-04-03 16:58                           ` Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2009-03-31 13:24 Jan Buchal

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=878wmjph80.fsf@mundaneum.com \
    --to=zthjwsqqafhv-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).