;convert extant addon tests to shellrunner format 3
This commit is contained in:
		
							parent
							
								
									4593963fef
								
							
						
					
					
						commit
						c6da152e9a
					
				| @ -4,24 +4,24 @@ | ||||
| # they always run the first hledger executable in PATH | ||||
| 
 | ||||
| # 1. flags after an add-command are handled by the add-on | ||||
|  PATH=$PATH:. hledger addon --help | ||||
| >>> /hledger-addon/ | ||||
| >>>=0 | ||||
| $ PATH=$PATH:. hledger addon --help | ||||
| > /hledger-addon/ | ||||
| >=0 | ||||
| 
 | ||||
| # 2. add-on flags which are not also defined in the main executable are a problem | ||||
|  PATH=$PATH:. hledger addon --addonflag | ||||
| >>>2 /Unknown flag: --addonflag/ | ||||
| >>>=1 | ||||
| $ PATH=$PATH:. hledger addon --addonflag | ||||
| >2 /Unknown flag: --addonflag/ | ||||
| >=1 | ||||
| 
 | ||||
| # 3. hledger main executable ignores anything after -- (and hides the -- from the add-on) | ||||
|  PATH=$PATH:. hledger addon --help -- --addonflag | ||||
| >>> /hledger-addon/ | ||||
| >>>=0 | ||||
| $ PATH=$PATH:. hledger addon --help -- --addonflag | ||||
| > /hledger-addon/ | ||||
| >=0 | ||||
| 
 | ||||
| # TODO how to reliably ensure no addons but still find the hledger executable ? | ||||
| # 4. having no addons shouldn't break the commands list | ||||
| # PATH= ~/.local/bin/stack exec -- hledger | ||||
| #>>>=0 | ||||
| # $ PATH= ~/.local/bin/stack exec -- hledger | ||||
| # >=0 | ||||
| 
 | ||||
| # ############################    issue 457    ##################################### | ||||
| #                                                                                  # | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user