From c73744938eca1f3796d702eff2c65b5c35886413 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Tue, 24 Sep 2024 21:32:26 -1000 Subject: [PATCH] ;doc: timedot: mention the common journal+timedot file setup [#2238] --- hledger/hledger.m4.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index ac231a850..8004a0e09 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -4386,7 +4386,6 @@ To generate time logs, ie to clock in and clock out, you could: # Timedot - `timedot` format is hledger's human-friendly time logging format. Compared to [`timeclock` format](#timeclock), it is 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". No commodity symbol is assumed, but we typically interpret it as hours. - ```cli $ hledger -f a.timedot print # .timedot file extension (or timedot: prefix) is required 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. 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 Numbers: