-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think I found an error in the documentation for -b and -e that may be important for some as we enter tax season.
,----[ info ledger ] | `--begin DATE' (`-b DATE') constrains the report to entries on or | after DATE. Only entries after that date will be calculated, which | means that the running total in the balance report will always start at | zero with the first matching entry. (Note: This is different from | using `--display' to constrain what is displayed). | | `--end DATE' (`-e DATE') constrains the report so that entries on or | after DATE are not considered. The ending date is inclusive. `---- I take the -b part to say that entries on or after the specified date will be included, but the "Only entries on or after that date will be calculated" is a bit confusing: I presume you mean that you'll report the entries for that date, but running calculations start with 0 on that date (reg report) and the _calculations_ start later. I take the -e part to say either that entries on or after that date will not be considered or that the ending date is inclusive, which tells me that that date will be included. IOW, it selects either [b,e] or [b,e), and I can't tell which, and I could see (b,e] or (b,e) as possibly correct. Running an experiment, I have to end a report on 2009/01/01 to see data - From 2008/12/31, which suggests [b,e) is correct. ,---- | $ ledger -v | Ledger 2.6.1, the command-line accounting tool `---- Bill - -- Bill Harris http://facilitatedsystems.com/weblog/ Facilitated Systems Everett, WA 98208 USA http://facilitatedsystems.com/ phone: +1 425 337-5541 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAklaVagACgkQ3J3HaQTDvd9d1gCfXU4GfFsvj5LmnGtZJYE+uewT nwwAnAzvPJr+LxVjDHGzcyzeaYrXiXt4 =uEy7 -----END PGP SIGNATURE-----
