You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm wondering how feasible it would be to export to ledger time format. Ledger is a CLI accounting tool that could then take care of filtering and aggregating issues. It has many ports; the original and hledger (Haskell) claim to have this time log functionality.
See: http://hledger.org/manual.html#timelog The format is as follows (C&P from there):
i 2015/03/30 09:00:00 some:account name optional description after two spaces
o 2015/03/30 09:20:00
i 2015/03/31 22:21:45 another account
o 2015/04/01 02:00:34
I have taken a look at the json file ti creates and on first glance it seems like the conversion would be straightforward to implement. Now I read a bit more here, for instance about interrupts and I'm not so sure anymore. Are interruptions handled before we even write to the json store? Or only when log aggregates? In other words can I produce such a file by parsing straight through the json file or will there be some traps waiting for me?
Ok, I'm looking at how interrupts are actually logged now. I'd have to remove the color coding and parse to the original account so they're not mixed. It appears that ti log has the same issue however. I get the following unexpected/non-aggregated output:
I don't like having the interrupt in the task name. I think it is unnecessary and it causes problems like this. The color coding shouldn't ever be stored in the JSON. I think that is a bug in the way interrupts are being added.
Fixed bug where interrupt creation was passing a colorized name into action_on,
which in turn was storing color codes in the JSON store.
Referenced by sharat87#13.
Hi,
I'm wondering how feasible it would be to export to ledger time format. Ledger is a CLI accounting tool that could then take care of filtering and aggregating issues. It has many ports; the original and hledger (Haskell) claim to have this time log functionality.
See: http://hledger.org/manual.html#timelog The format is as follows (C&P from there):
I have taken a look at the json file ti creates and on first glance it seems like the conversion would be straightforward to implement. Now I read a bit more here, for instance about interrupts and I'm not so sure anymore. Are interruptions handled before we even write to the json store? Or only when log aggregates? In other words can I produce such a file by parsing straight through the json file or will there be some traps waiting for me?
Ok, I'm looking at how interrupts are actually logged now. I'd have to remove the color coding and parse to the original account so they're not mixed. It appears that
ti log
has the same issue however. I get the following unexpected/non-aggregated output:Best regards,
Matthias
The text was updated successfully, but these errors were encountered: