From 1c9a44cae94aa1773ea0c6734d7468b353f14a03 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Thu, 19 Jan 2023 05:55:29 -1000 Subject: [PATCH] ;doc: csv: try to clarify how CSV fields and hledger fields work --- hledger/hledger.m4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index 644348e68..21dbbbe55 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -3071,7 +3071,7 @@ Note the two kinds of "field names" used in hledger CSV rules: 1. **CSV field names** (`CSVFIELD` in examples):\ These are arbitrary names you have given to columns in the CSV data, by writing them in a `fields` list. This does not affect hledger's output (at least not directly); it only gives that CSV field a custom name, - so that elsewhere, in a hledger field assignment, you can interpolate it by name (`%SomeField`) rather than column number (`%13`). + so that elsewhere, in a field assignment rule, you can interpolate it by name (`%SomeField`) rather than column number (`%13`). 2. **hledger field names** (`HLEDGERFIELD` in examples):\ These are special reserved names corresponding (directly or indirectly) to parts of a hledger transaction.