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).
		
			
				
	
	
		
			24 lines
		
	
	
		
			678 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			24 lines
		
	
	
		
			678 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| # issue 219, --tree and --flat flags should override each other cleanly
 | |
| # 1. multiple flags ending with --flat, equivalent to --flat
 | |
| hledger -f balance-multicol.journal bal -MEH --no-total date:2013/1 --tree --flat
 | |
| >>>
 | |
| Ending balances (historical) in 2013/01:
 | |
| 
 | |
|                  ||  2013/01/31 
 | |
| =================++=============
 | |
|  assets:checking ||          10 
 | |
| 
 | |
| >>>= 0
 | |
| 
 | |
| # 2. multiple flags ending with --tree, equivalent to --tree
 | |
| hledger -f balance-multicol.journal bal -MEH --no-total date:2013/1 --flat --tree
 | |
| >>>
 | |
| Ending balances (historical) in 2013/01:
 | |
| 
 | |
|             ||  2013/01/31 
 | |
| ============++=============
 | |
|  assets     ||          10 
 | |
|    checking ||          10 
 | |
| 
 | |
| >>>= 0
 |