21d9945ba9
Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test).
29 lines
568 B
Plaintext
29 lines
568 B
Plaintext
# 1.
|
|
hledger -f sample.journal balance --no-total --depth 1
|
|
>>>
|
|
$-1 assets
|
|
$2 expenses
|
|
$-2 income
|
|
$1 liabilities
|
|
>>>=0
|
|
|
|
# 2. Depth 0 aggregates everything into one line
|
|
hledger -f sample.journal balance --no-total --depth 0
|
|
>>>
|
|
0 ...
|
|
>>>=0
|
|
|
|
# 3. Ditto in a multi-column balance report.
|
|
hledger -f sample.journal balance -M -e 2008/4 --depth 0
|
|
>>>
|
|
Balance changes in 2008/01:
|
|
|
|
|| 2008/01
|
|
=====++==========
|
|
... || 0
|
|
-----++----------
|
|
|| 0
|
|
|
|
>>>=0
|
|
|