Office hours vs. Work hours

First of all, sorry for taking so long to reply to your bug report.

How about this: a new setting in .gtimelogrc

    break_hours = 1

and then I change the computation of the "left/overtime" bit to be (hours + break_hours) - (total_work + total_slacking + time_since_last_task_was_completed)? Does that sound acceptable?

That sounds good. I assume, break_hours will be a float value, so that a half hour break can be specified by 0.5?

What about break_time set in minutes?

I think a better idea would be to have a work_hours and office_hours setting, either of which could be blank.

work_hours is the amount of time that should be worked (not ** or *** time)

office_hours is the amount of time that you should be in the office (time since 'arrived', including "coffee break **", but maybe not "run errand ***" time?)

I don't think baking in more assumptions about work days being continuous is useful, which is what the break_hours looks like to me.

I work flexible hours from home, so the the "hours left" is meaningless for me, the only thing is how many hours I work a week (40+), and I basically only pay attention to the 'time left at work' and 'total work done' lines, everything else is meaningless.

Rght now I watch the total work done "per day", which has to hit 8h/day. To see how much remains in a week of work, I still have to do arithmetic, either multiplying the number of work days this week times 8 and subtracting total work done "this week", or else take the 8- the "total work per day", and multiply by the number of days I've worked.

Moved to https://github.com/gtimelog/gtimelog/issues/46 (I find Launchpad's bug tracker unappealing and basically never go look at it.)