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).
		
			
				
	
	
		
			52 lines
		
	
	
		
			1001 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			52 lines
		
	
	
		
			1001 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| # --flat shows inclusive balances; total balance should be that of top-level accounts (issue 94)
 | |
| # # 1. 
 | |
| # hledger -f - balance --flat
 | |
| # <<<
 | |
| # 1/1
 | |
| #     (a)     1
 | |
| #     (a:aa)  1
 | |
| # >>>
 | |
| #                    2  a
 | |
| #                    1  a:aa
 | |
| # --------------------
 | |
| #                    2
 | |
| # >>>= 0
 | |
| 
 | |
| # --flat shows exclusive balances
 | |
| # 1. 
 | |
| hledger -f - balance --flat
 | |
| <<<
 | |
| 1/1
 | |
|  (a:aa)       1
 | |
|  (a:aa:aaa)   1
 | |
|  (a:aa:bbb)   1
 | |
|  (b)          1
 | |
|  (b:bb:bbb)   1
 | |
| >>>
 | |
|                    1  a:aa
 | |
|                    1  a:aa:aaa
 | |
|                    1  a:aa:bbb
 | |
|                    1  b
 | |
|                    1  b:bb:bbb
 | |
| --------------------
 | |
|                    5
 | |
| >>>= 0
 | |
| 
 | |
| # --flat --depth shows the same accounts, but clipped and aggregated at the depth limit
 | |
| # 2. 
 | |
| hledger -f - balance --flat --depth 2
 | |
| <<<
 | |
| 1/1
 | |
|  (a:aa)       1
 | |
|  (a:aa:aaa)   1
 | |
|  (a:aa:bbb)   1
 | |
|  (b)          1
 | |
|  (b:bb:bbb)   1
 | |
| >>>
 | |
|                    3  a:aa
 | |
|                    1  b
 | |
|                    1  b:bb
 | |
| --------------------
 | |
|                    5
 | |
| >>>= 0
 |