032ffd112b
Eg, where previously -p 'monthly from 1/15' or -M -b 1/15 would always adjust the report start date to 1/1, unless you used the special -p 'every 15th day of month from 1/15' form, now the start date will not be adjusted. (It is still adjusted if the report date is not specified explicitly, eg inferred from the journal). This keeps behaviour consistent between report periods and periodic transactions. 'in' period expressions, like 'in 2023-01', are a grey area; they do specify a start date (2023-01-01), although they look a bit implicit. So previously, -p 'weekly in 2023-01' would adjust the start date to the preceding monday (2022-12-26), but now it will start exactly on 2023-01-01 (a sunday, which also causes ugly verbose column headings). To ensure monday based weeks and simple report headings here, you would have to explicitly specific a start date that is a monday, eg -p 'weekly from 2022-12-26 to 2023-02'. |
||
|---|---|---|
| .. | ||
| Hledger | ||
| other/ledger-parse | ||
| test | ||
| Text | ||
| .date.m4 | ||
| .ghci | ||
| .version | ||
| .version.m4 | ||
| CHANGES.md | ||
| hledger-lib.cabal | ||
| Hledger.hs | ||
| LICENSE | ||
| package.yaml | ||
| README.md | ||
| Setup.hs | ||
hledger-lib
A reusable library containing hledger’s core functionality. This is used by most hledger* packages so that they support the same common file formats, command line options, reports etc.
See also: the project README and home page.