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).
40 lines
831 B
Plaintext
40 lines
831 B
Plaintext
# 1. all data files on the command line should be read
|
|
hledger inc -f personal.journal -f business.journal
|
|
>>>
|
|
Income Statement
|
|
|
|
Revenues:
|
|
--------------------
|
|
0
|
|
|
|
Expenses:
|
|
$2 expenses
|
|
$1 food
|
|
$1 office supplies
|
|
--------------------
|
|
$2
|
|
|
|
Total:
|
|
--------------------
|
|
$2
|
|
>>>2
|
|
>>>=0
|
|
|
|
# 2. aliases in files should only apply to later files
|
|
hledger print -f personal.journal -f business.journal -f alias.journal -f personal.journal
|
|
>>>
|
|
2014/01/01
|
|
expenses:office supplies $1
|
|
assets:business checking $-1
|
|
|
|
2014/01/02
|
|
expenses:food $1
|
|
assets:cash $-1
|
|
|
|
2014/01/02
|
|
equity:draw:personal:food $1
|
|
assets:personal:cash $-1
|
|
|
|
>>>2
|
|
>>>=0
|