arbtt-stats --intervals time format

[nomeata]

Original report by amenthes (Bitbucket: amenthes, GitHub: amenthes).

---

This one is also related to he --intervals command. The output appears to be american date format "Month/Day/Year Hour:Minute:Second"

Program:firefox | 08/30/15 12:58:42 | 08/30/15 12:59:42 |    2m00s

I think there should be a way to get this info in local format or even better in iso8601 format.

"2012-04-21T18:25:43-05:00"

This has two advantages: it sorts nicely and more importantly, it also contains the timezone.

To prevent breaking existing workflows, this should probably be an option or a flag.

[nomeata]

Original comment by nomeata (Bitbucket: nomeata, GitHub: nomeata).

---

Also valid, although I have to first find out how to actually get the locale information here.

[nomeata]

Original comment by Martin von Wittich (Bitbucket: martinvonwittich, GitHub: martinvonwittich).

---

I was just about to file a bug on https://github.com/nomeata/arbtt/issues, but luckily found this issue here before posting. (Which raises the question: which bug tracker is the right one? Having two at the same time is kinda confusing.)

Currently, the timestamp format of arbtt-stats --interval is inconsistent with the rest of arbtt; everything else seems to default to ISO8601 %Y-%m-%d:

martin@martin ~ % arbtt-stats --dump-samples 2>/dev/null | grep '^2021' | tail -n1
2021-06-01 18:41:39 (33ms inactive):
martin@martin ~ % arbtt-dump | grep '^2021' | tail -n1                            
2021-06-01 18:41:39 (33ms inactive):
martin@martin ~ % arbtt-stats --for-each day 2>/dev/null | grep 'Total time per tag' | tail -n1
Total time per tag (Day 2021-06-01)

IMO a quick fix that just changes the default format to ``%Y-%m-%d\ would be preferable until proper locale support can be implemented. I would even argue that the default text output of arbtt-stats doesn’t need to have an option for the timestamp format because it’s not supposed to be parsed anyway, but for --output-format tsv / csv it’s probably a different story :/

‌

[nomeata]

Original comment by nomeata (Bitbucket: nomeata, GitHub: nomeata).

---

(Which raises the question: which bug tracker is the right one? Having two at the same time is kinda confusing.)

Yeah… I put this on Bitbucket at a time when Github wasn’t quite the monopoly yet, and I was hoping I could help with keeping the landscape diverse. But in practice, that didn’t quite work out. I should probably move the projects to Github completely.

I wounld’t mind a patch that make the time display consistent.

[nomeata]

Ok, migrated to Github. Hope you’ll find it here :-)