Re: "A valid price for … could not be found"

Yes. (See Note: from 3rd message in thread :-)) On Fri, Oct 14, 2016 at 11:33 PM, Matthew Harris wrote: > Aha. With "bean-query print" I was able to determine that I needed to put > the implicit_prices plugin before the unrealized plugin. Now I'm > warning-free. Thank you!

Re: "A valid price for … could not be found"

Aha. With "bean-query print" I was able to determine that I needed to put the implicit_prices plugin before the unrealized plugin. Now I'm warning-free. Thank you! On Friday, October 14, 2016 at 6:40:50 PM UTC-7, Martin Blais wrote: > > On Fri, Oct 14, 2016 at 1:14 PM, Matthew Harris

Re: "A valid price for … could not be found"

On Fri, Oct 14, 2016 at 1:14 PM, Matthew Harris wrote: > In the Language manual, you say a Price directive is synthesized when a > posting has a cost or price. But I get the "A valid price for HOUSE/USD > could not be found" warning with > > 2005-05-24 * "Home Purchase" >

Re: "A valid price for … could not be found"

In the Language manual, you say a Price directive is synthesized when a posting has a cost or price. But I get the "A valid price for HOUSE/USD could not be found" warning with 2005-05-24 * "Home Purchase" Assets:Home 1 HOUSE {10.00 USD} Liabilities:Mortgage -10.00 USD and

Re: "A valid price for … could not be found"

Matthew: This is not a bug, but rather a choice I made a while ago that instead of silently ignoring the unrealized gains if you didn't provide some price information, to warn about it instead:

Re: "A valid price for … could not be found"

I had to use the add_implicit_prices plugin ( https://bitbucket.org/blais/beancount/src/5e2dcbfc81b15cfbaa9d743ee87d8f4f26eaf0cb/src/python/beancount/plugins/implicit_prices.py?at=default=file-view-default) to turn entries like these into prices. You should try out my unrealized_periodic plugin (