From d13b334fb23fac29d08a4104b26a4e2182ad2037 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Wed, 16 Apr 2025 16:43:57 -1000 Subject: [PATCH] ;doc:csv: How CSV rules are evaluated: clarify --- hledger/hledger.m4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index f94a309b1..09a45204b 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -4279,13 +4279,13 @@ If you get a confusing error while reading a CSV file, it may help to try to und - For each hledger field (`date`, `description`, `account1`, etc.): - 1. Collect all assignments to this field, + 1. Get the field's assigned value, first searching top level assignments, made directly or by the `fields` rule, then assignments made inside succeeding `if` blocks. If there are more than one, the last one wins. 2. Compute the field's actual value (as text), - by interpolating any %CSVFIELD references within the assigned value, + by interpolating any %CSVFIELD references within the assigned value; or by choosing a default value if there was no assignment. - Generate a hledger transaction from the hledger field values,