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
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,6 +82,7 @@ Options can either be used from command line or in configuration file.
82
82
--effective-date INT CSV column number matching effective date
83
83
--encoding STR text encoding of CSV input file
84
84
--incremental append output as transactions are processed
85
+
--ledger-binary FILE path to ledger binary
85
86
--ledger-date-format STR
86
87
date format for ledger output file
87
88
--ledger-decimal-comma
@@ -235,6 +236,11 @@ the transaction description) in an encoding other than UTF-8.
235
236
236
237
appends output as transactions are processed. The default flow is to process all CSV input and then output the result. When `--incremental` is specified, output is written after every transaction. This allows one to stop (ctrl-c) and restart to progressively process a CSV file (`--skip-dupes` is a useful companion option).
237
238
239
+
**`--ledger-binary`**
240
+
241
+
is the path to the ledger binary. Not neccessary if it is in `PATH` or is at either `/usr/bin/ledger` or
242
+
`/usr/local/bin/ledger`
243
+
238
244
**`--ledger-date-format STR`**
239
245
240
246
describes the date format to be used when creating ledger entries. If
0 commit comments