;doc: timedot: mention the common journal+timedot file setup [#2238]

This commit is contained in:
Simon Michael 2024-09-24 21:32:26 -10:00
parent e6f988406f
commit c73744938e

View File

@ -4386,7 +4386,6 @@ To generate time logs, ie to clock in and clock out, you could:
# Timedot # Timedot
`timedot` format is hledger's human-friendly time logging format. `timedot` format is hledger's human-friendly time logging format.
Compared to [`timeclock` format](#timeclock), it is Compared to [`timeclock` format](#timeclock), it is
more convenient for quick, approximate, and retroactive time logging, more convenient for quick, approximate, and retroactive time logging,
@ -4404,7 +4403,6 @@ hledger reads this as a transaction on this day with three
(unbalanced) postings, where each dot represents "0.25". (unbalanced) postings, where each dot represents "0.25".
No commodity symbol is assumed, but we typically interpret it as hours. No commodity symbol is assumed, but we typically interpret it as hours.
```cli ```cli
$ hledger -f a.timedot print # .timedot file extension (or timedot: prefix) is required $ hledger -f a.timedot print # .timedot file extension (or timedot: prefix) is required
2023-05-01 * 2023-05-01 *
@ -4463,6 +4461,11 @@ There is some flexibility to help with keeping time log data and notes in the sa
(one or more `*`'s followed by a space) will be ignored. (one or more `*`'s followed by a space) will be ignored.
This means the time log can also be a org outline. This means the time log can also be a org outline.
Timedot files don't support directives like journal files.
So a common pattern is to have a main journal file (eg `time.journal`)
that contains any needed directives,
and then [includes](#include-directive) the timedot file (`include time.timedot`).
## Timedot examples ## Timedot examples
Numbers: Numbers: