On Monday, December 29, 2014 10:19:41 PM UTC+1, Martin Michlmayr wrote:
>
> * guivho <[email protected] <javascript:>> [2014-12-29 10:58]: 
> > The anon.ledger file in appendix does not pre-define accounts, 
> commodities 
> > nor payees. 
> > 
> > Thus the command 
> > ledger --pedantic --check-payees bal -f anon.ledger 
> > should throw errors about accounts, commodity and payees, at least 
> that's 
> > what I read at 
> > 
> http://www.ledger-cli.org/3.0/doc/ledger3.html#Error-Checking-and-Calculation-Options
>  
> <http://www.google.com/url?q=http%3A%2F%2Fwww.ledger-cli.org%2F3.0%2Fdoc%2Fledger3.html%23Error-Checking-and-Calculation-Options&sa=D&sntz=1&usg=AFQjCNFnnK2E5NBl8L98W0GGR_6u_kvwOQ>
>  
>
> I'll quote an answer I received when I asked about this: "This needs 
> to be documented but currently --explicit only has an effect if there 
> are any pre-declarations for the corresponding type (accounts, …):" 
>
> I reported this issue as http://bugs.ledger-cli.org/show_bug.cgi?id=771 
> but it arguably works as designed and just needs to be documented. 
>
> I now tried the --explicit option and it does indeed work. 

Didn't know about it while it's documentation in section 8.3.2 at 
http://www.ledger-cli.org/3.0/doc/ledger3.html#Session-Options says

FIX THIS ENTRY

I do not know enough about it to propose a fix for it.

What's more, apparently --explicit seems to cover the other three options: 
neither --strict, --pedantic nor --check-payees seem to be needed. 

Just specifying --explicit cause ledger to bark for undeclared accounts, 
commodities and payees. 

And it probably is wise enough to only check for either of them if there 
are predeclared values. I sure can live with that behavior, seems very 
sensible to me.

Thanks Martin.


Guido
  
 

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to