Can you reproduce this error using a file with only this single booking? If
so, could you provide that file, so I can fiddle with it myself?

On Wed Nov 26 2014 at 9:24:02 PM guivho <[email protected]> wrote:

> Hi,
>
> I do not understand why I get following error:
>
> {
> $ ledger -v
>     0ms  [INFO]  Ledger starting
>     0ms  [INFO]  Parsing file "/Users/guivho/.ledgerrc"
> Ledger 3.0.0-20120510, the command-line accounting tool
>
> Copyright (c) 2003-2012, John Wiegley.  All rights reserved.
>
> This program is made available under the terms of the BSD Public License.
> See LICENSE file included with the distribution for details and disclaimer.
>     1ms  [INFO]  Parsing file "/Users/guivho/ledger/boekhouding.ledger"
> While parsing file "/Users/guivho/ledger/boekhouding.ledger", line 76907:
> Error: A posting's cost must be of a different commodity than its amount
>   507ms  [INFO]  Ledger ended
> }
>
> The offending line 76907 is:
> {
>     t:colruyt                                €-276.04
> }
>
> It's the last post of a grocery ticket. I use € as commodity for all
> nearly all my posts. This post only differs from many previous posts in the
> amount. I can avoid the error by just omitting the amount. But I like to
> mention it as an easy check that I didn't goof up when entering the other
> posts of the grocery ticket. And anyway I'm puzzled by the fact that this
> particular post triggers this error for no apparent reason (at least
> i.m.h.o.)
>
> Any ideas?
>
> 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.
>

-- 

--- 
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