Give an early pointer to where to look if 'acprep update' fails.
Clarify a few things in the first section.
Give sections clearer headers, so they can be more easily referred to.
Add a FAQ entry about what to do if './acprep update' gives errors.
Update FAQ entry about MPFR library to refer to above new entry.
'filename' returns the complete path/filename of the file containg the current xact.
This is inconvenient for some displays. filebase returns only the base name. For
completeness added filepath as well.
This was caused by both 'A' and 'bucket' using
default_account_directive. This function was still stripping the 'A'
directive, so the first character of the account name used with 'bucket'
was cut off. Maybe the code for the other directives should be changed
accordingly for consistency (put line + 1 in call instead of function).
If the command line switch "-f" is used the test runner will
not pass the file name of the test file to ledger.
The line "test -f /dev/null" as used in test/baseline/cmd-convert.test
did not work as intended before this.
Also using "-f - " did not work as "$ledger" was noti
prepended to the command.
By using payees_for_unknown_accounts instead of account_mappings in
csv.cc ledger will have the same behaviour as in `ledger -f - print`
in that it uses payee fields in account directives to rewrite the
account.
test/regress/CAE63F5C-b.test and test/regress/CAE63F5C-c.test should both
pass, but test/regress/CAE63F5C-c.test does not, because the total line of
$6.46 is rounded wrong; it should be $6.45.
There seems to be different rounding occurring for totals vs. postings.
This seems to be related to Bug #492.
Due to weirdness that's currently true with the existing next branch of
ledger, I believe it's important to tell users in the documentation that
there are some discrepancies in the 'fixed' directive behavior.
The documentation from my previous commit is written to explain what
'fixed' *should* do; adding the bug report link here is a placeholder to
tell users that it may not do what they think it does.
Obviously, if someone closes#789, they should remove this paragraph added
herein. But, if the bug report is closed, but the documentation lags
behind, the worst that happens is some users have to click through to see
the bug is closed.
doc/ledger3.info was probably missing from the .gitignore because
ledger3.info isn't build automatically yet, but might as well add it to
.gitignore for those who are building it by hand at the moment.
Change the column of Receipt and Invoice in the CSV file first, then the
generated ODS file must have the same change propagated, which requires
changes to the column numbers hard-coding in csv2ods.py.
Perhaps if/when this application is refactored these things shouldn't be
hard-coded in this way in the first place.
