Idea for handling stuff that happens while not logged in

Christian arbtt at konzertheld.de
Sat Feb 23 00:03:49 CET 2019


Hello everyone,

sorry for double posting right with my first message to the list. My
last mail was unfinished, as you could see.

I recently figured out how to build arbtt on Arch and am now a happy
user on both my private and my work laptop. For the latter, I am
planning to use the arbtt-stats --intervals report to do my hours
reporting. I am currently using normal stats based on tags, but as you
can never catch 100%, I will use the intervals and pull untagged parts
to the closest tagged time period.

So much for introduction. What this can not do for me is of course
taking care of stuff I do while not on my laptop. For that, I have
developed a little script that will allow me to enter a comment on what
I did while I was away every time I unlock my screen. The idea is to
combine that with the "inactive" intervals from arbtt to get a report
that is very close to what I actually did and to how much time I
actually spent working.

I wonder what combination of tools would be good to achieve this. I
could use arbtt-stats and write something completely new myself to
combine its output with the data my tool collected but maybe there is a
nicer solution, using existing tools or something built into arbtt. I
could imagine some kind of interface to tell arbtt what happened while
the PC was locked. I also remember some discussion about logging the
lock screen "window":
https://bitbucket.org/nomeata/arbtt/issues/29/lock-screen-and-machine-off-standby

Has there been any follow-up? Would it be worth a try to integrate the
"locked time" log with arbtt-graph? And generally, what do you think of
the idea? I'm curious for both input and general feedback. :-)

Happy hacking,
Christian




More information about the arbtt mailing list