Timewarrior 'lunch' feature

28 views
Skip to first unread message

Paul Beckingham

unread,
Nov 9, 2017, 5:20:09 PM11/9/17
to taskwar...@googlegroups.com
Thomas,

Just saw this question on IRC:


Seems reasonable to me.  Would you have a better suggestion?

I guess ‘break’ would be a better name, but it’s all about lunch in this question.

Paul

Dirk Deimeke

unread,
Nov 9, 2017, 11:56:18 PM11/9/17
to taskwar...@googlegroups.com
On 09.11.2017 23:20, Paul Beckingham wrote:

Hi Paul,

> Seems reasonable to me.  Would you have a better suggestion?

what about having a period of time tagged as "break" or "lunch"?

> I guess ‘break’ would be a better name, but it’s all about lunch in this
> question.

I second "break".

Cheers

Dirk

--
https://d5e.org/

Thomas Lauf

unread,
Nov 10, 2017, 12:47:05 AM11/10/17
to taskwar...@googlegroups.com
Hi Paul!

If the user does not want to track his/her breaks

timew stop
timew continue

does the job. If tracking is desired

timew start LUNCH/BREAK/PAUSE/...
timew continue [<id>]

is the command at hand (which I use for example). With TI-90, also

timew start PAUSE
timew continue @3 12:03

would be possible.

In this case I would rather focus on the summary command, because then
the sums are skewed by the extra time-off intervals. Currently, it looks
like this:

Wk Date Day ID Tags Start End Time Total
--- ---------- --- --- ------------ -------- -------- ------- --------
W45 2017-11-06 Mon @14 PROJECT, FOO 8:24:00 11:36:00 3:12:00
@13 PAUSE 11:36:00 12:06:00 0:30:00
@12 PROJECT, FOO 12:06:00 14:09:00 2:03:00 5:45:00
W45 2017-11-07 Tue @11 PROJECT, FOO 7:57:00 11:48:00 3:51:00
@10 PAUSE 11:48:00 12:21:00 0:33:00
@9 PROJECT, FOO 12:21:00 17:12:00 4:51:00 9:15:00
W45 2017-11-08 Wed @8 PROJECT, BAR 8:09:00 10:36:00 2:27:00
@7 PROJECT, BAR 10:36:00 11:39:00 1:03:00
@6 PAUSE 11:39:00 12:12:00 0:33:00
@5 PROJECT, BAR 12:12:00 17:45:00 5:33:00 9:36:00
W45 2017-11-09 Thu @4 PROJECT, FOO 8:42:00 12:06:00 3:24:00
@3 PAUSE 12:06:00 12:42:00 0:36:00
@2 PROJECT, FOO 12:42:00 14:06:00 1:24:00
@1 PROJECT, FOO 14:06:00 18:30:00 4:24:00 9:48:00

34:24:00

But I would rather have something like this:

Wk Date Day ID Tags Start End On Off Total
--- ---------- --- --- ------------ ----- ----- ---- ---- -----
W45 2017-11-06 Mon @14 PROJECT, FOO 8:24 11:36 3:12
@13 PAUSE 11:36 12:06 0:30
@12 PROJECT, FOO 12:06 14:09 2:03 5:15
W45 2017-11-07 Tue @11 PROJECT, FOO 7:57 11:48 3:51
@10 PAUSE 11:48 12:21 0:33
@9 PROJECT, FOO 12:21 17:12 4:51 8:42
W45 2017-11-08 Wed @8 PROJECT, BAR 8:09 10:36 2:27
@7 PROJECT, BAR 10:36 11:39 1:03
@6 PAUSE 11:39 12:12 0:33
@5 PROJECT, BAR 12:12 17:45 5:33 9:03
W45 2017-11-09 Thu @4 PROJECT, FOO 8:42 12:06 3:24
@3 PAUSE 12:06 12:42 0:36
@2 PROJECT, FOO 12:42 14:06 1:24
@1 PROJECT, FOO 14:06 18:30 4:24 9:12

32:12


As an alternative to alter the summary command, one could put this into
an extension...

Regards
Thomas

signature.asc

Thomas Hochstein

unread,
Nov 10, 2017, 3:18:30 AM11/10/17
to taskwar...@googlegroups.com
On 2017-11-10 06:46, Thomas Lauf wrote:
> If tracking is desired
>
> timew start LUNCH/BREAK/PAUSE/...
> timew continue [<id>]
>
> is the command at hand (which I use for example).
[...]
> In this case I would rather focus on the summary command, because then
> the sums are skewed by the extra time-off intervals. Currently, it
> looks
> like this:
>
> Wk Date Day ID Tags Start End Time Total
> --- ---------- --- --- ------------ -------- -------- ------- --------
> W45 2017-11-06 Mon @14 PROJECT, FOO 8:24:00 11:36:00 3:12:00
> @13 PAUSE 11:36:00 12:06:00 0:30:00
> @12 PROJECT, FOO 12:06:00 14:09:00 2:03:00 5:45:00
[...]
> But I would rather have something like this:
>
> Wk Date Day ID Tags Start End On Off Total
> --- ---------- --- --- ------------ ----- ----- ---- ---- -----
> W45 2017-11-06 Mon @14 PROJECT, FOO 8:24 11:36 3:12
> @13 PAUSE 11:36 12:06 0:30
> @12 PROJECT, FOO 12:06 14:09 2:03 5:15
[...]

What about a new flag to set to mark a time as "break" or "Off",
so you can do a

timew start --offtime LUNCH/BREAK/PAUSE/...

and that task is counted as "Off" for the summary? That would
make it possible to track "time off", and you can tag this time
as "break", "lunch", "doing a walk" or whatever, too.

Regards,
-thh

Thomas Lauf

unread,
Nov 10, 2017, 3:29:04 AM11/10/17
to taskwar...@googlegroups.com
Hi!

> What about a new flag to set to mark a time as "break" or "Off",
> so you can do a
>
>    timew start --offtime LUNCH/BREAK/PAUSE/...
>
> and that task is counted as "Off" for the summary? That would
> make it possible to track "time off", and you can tag this time
> as "break", "lunch", "doing a walk" or whatever, too.
>
Rather than adding a flag to the start command, I would add a config entry

timew.summary.ignore: LUNCH, BREAK, PAUSE, ...

and make timew summary ignore the intervals with tags listed here.
Keeps the command line simple :)


Regards

Thomas

signature.asc

Paul Beckingham

unread,
Nov 10, 2017, 8:54:22 AM11/10/17
to taskwar...@googlegroups.com

> Rather than adding a flag to the start command, I would add a config entry
>
> timew.summary.ignore: LUNCH, BREAK, PAUSE, ...
>
> and make timew summary ignore the intervals with tags listed here.
> Keeps the command line simple :)

That’s a great idea.

P
Reply all
Reply to author
Forward
0 new messages