1
0

getting started faq: edits

This commit is contained in:
Simon Michael
2024-01-17 10:53:57 -10:00
parent 209821b268
commit e756e34635

View File

@@ -67,7 +67,7 @@ In the above cases, all of the files are still read together as a single file se
and there is no reduction in data size or run time. For that, you must split by time.
This adds some complications, and isn't necessary for everyone, so we don't recommend it from the start.
But, most PTA users sooner or later will split files by time, and most of them will split by year.
But, most PTA users sooner or later will split files by time, and usually by year.
You might have an `all.journal` including all of the years, but also you can now choose
to read just one year or a subset of years when running reports, which is more efficient.
The new complication is how to arrange for correct account balances no matter which year file(s) you are processing.
@@ -117,6 +117,10 @@ msft.journal
...
```
If you use a lot of CSV files or hledger CSV rules, you might want `csv/` or `rules/` subdirectories.
Or you might be using one of the third-party setups like hledger-flow, which define their own file layouts.
See also:
- https://ledger-cli.org/doc/ledger3.html#Archiving-Previous-Years