From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Clocking work time vs. office time
Date: Fri, 29 Apr 2016 20:10:15 +0200 [thread overview]
Message-ID: <8lkcvcxdvt.ln2@news.c0t0d0s0.de> (raw)
In-Reply-To: 87lh3wv6ci.fsf@mbork.pl
Hello,
Marcin Borkowski <mbork@mbork.pl> writes:
> On 2016-04-29, at 11:21, Michael Welle <mwe012008@gmx.net> wrote:
>
>> Hello,
>>
>> Marcin Borkowski <mbork@mbork.pl> writes:
>>
>>> Hi list,
>>>
>>> I'm seeking ideas/workflows for a situation where I work partly in
>>> office and partly remotely. I'd like to be able to generate a report
>>> with information about both my work time and "office time". I know that
>>> you can't have two things clocked at the same time, so simply clocking
>>> "office time" and (during this office time) clocking e.g. individual
>>> tasks won't work.
>>>
>>> Any ideas?
>> I assume that you use a laptop or some other portable device? In that
>> case you can grep the IP address (which might change when you change
>> workplaces) and timestamps from the log files (or create a script that
>> logs the IP address changes to an ORG file) and then somehow (coughcough)
>> integrate that into your report.
>
> That's actually an interesting (and not standard) idea. Even moreso
> because I'm writing a RescueTime-like time-tracking tool for Emacs,
> working (unlike Org's clocking) without manual intervention - recording
> the state of computer (i.e., current idle time, active X window, active
> Emacs buffer name and mode) at regular (or not) intervals and making
> reports. I did not include any network-related info, but this would be
> easy to add. Thanks, I'll definitely think about it!
interesting.
I used the IP address approach for some time to track the time I spent
at customers sites. It worked quite well. The only trouble was if we
went to the cafeteria and talked for an hour before I had a chance to
start my laptop :).
Regards
hmw
next prev parent reply other threads:[~2016-04-29 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 7:29 Clocking work time vs. office time 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 [this message]
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
[not found] <8a62af79ec0b4d3d9e2c2e83a053f889@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-29 9:16 ` 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
2016-04-29 12:24 ` Marcin Borkowski
2016-04-29 15:13 ` Stefan Nobis
2016-04-29 19:58 ` Marcin Borkowski
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=8lkcvcxdvt.ln2@news.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--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).