From: Marcin Borkowski <mbork@mbork.pl>
To: Peter Neilson <neilson@windstream.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clocking work time vs. office time
Date: Fri, 29 Apr 2016 16:23:50 +0200 [thread overview]
Message-ID: <87mvocv6h5.fsf@mbork.pl> (raw)
In-Reply-To: <op.ygok2llsrns8nc@odin>
On 2016-04-29, at 14:31, Peter Neilson <neilson@windstream.net> wrote:
> On Fri, 29 Apr 2016 08:08:38 -0400, Loris Bennett
> <loris.bennett@fu-berlin.de> wrote:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> On Friday, 29 Apr 2016 at 09:25, Marcin Borkowski wrote:
>>>> However, this does not help with my main issue: tracking /time in
>>>> office/. Not /time in office working/, mind you.
>>>>
>>>> I'd like to have a report like this (I mean information, not
>>>> formatting):
>>>>
>>>> * Office time: 2:00
>>>> ** Task 1/Project A: 0:30
>>>> ** Task 2/Project B: 0:45
>>>>
>>>> * Home time:
>>>> ** Task 1/Project A: 1:15
>>>> ** Task 2/Project B: 0:30
>>>>
>>>> So not only time spent on actual work on various tasks/projects, but
>>>> also time /spent physically in the office/.
>>>
>>> I would suggest that the office time simply be the sum of the times of
>>> all headlines within that sub-tree? If you need something to mop up
>>> times which are not allocated to a specific task within the office
>>> hierarchy, create a sub-headline called "misc" or some such?
>>>
>>> Or am I missing something more fundamental?
>>
>> For me the problem would be just checking in and out of "misc". If I
>> forget once, then my /time in the office/ would be incorrect.
>>
>> Personally, I need to keep track of /time in the office/ for my
>> employer. Tracking time actually spent doing tasks planned with Org
>> would be nice for me personally, but as I can't currently have two
>> clocks running, I don't do this.
>
> Have not tested this, but what about running two separate sessions of
> emacs? It would certainly work if using two separate machines or two
> separate logins on one machine. Should be able to ssh or ctrl-alt-F1 to a
> different identity. Merge the two reports into one later with easy custom
> code.
Thanks for the input, but I consider this to be a Very Bad Idea™.
I would be constantly annoyed by not shared histories, open buffers etc.
YMMV, of course.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2016-04-29 14:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a62af79ec0b4d3d9e2c2e83a053f889@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-29 9:16 ` Clocking work time vs. office time Eric S Fraga
2016-04-29 9:25 ` Marcin Borkowski
[not found] ` <7b8632d87e0d414e8c12b27aee1452b9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-29 11:05 ` Eric S Fraga
2016-04-29 12:08 ` Loris Bennett
2016-04-29 12:31 ` Peter Neilson
2016-04-29 14:23 ` Marcin Borkowski [this message]
2016-04-29 12:24 ` Marcin Borkowski
2016-04-29 15:13 ` Stefan Nobis
2016-04-29 19:58 ` Marcin Borkowski
2016-04-29 7:29 Marcin Borkowski
2016-04-29 9:21 ` Michael Welle
2016-04-29 14:26 ` Marcin Borkowski
2016-04-29 14:51 ` Brett Viren
2016-04-29 18:00 ` Michael Welle
2016-05-02 20:39 ` Marcin Borkowski
2016-04-29 18:10 ` Michael Welle
2016-04-29 19:55 ` Marcin Borkowski
[not found] ` <17pdvcxts5.ln2@news.c0t0d0s0.de>
2016-04-30 6:28 ` Marcin Borkowski
2016-04-29 20:13 ` Simon Thum
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvocv6h5.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=neilson@windstream.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.