On Wed, Sep 6, 2023 at 8:33 AM Daniele Nicolodi <dani...@grinta.net> wrote:

> On 06/09/23 16:54, Eric Altendorf wrote:
> >
> >
> > On Wed, Sep 6, 2023 at 04:00 Daniele Nicolodi <dani...@grinta.net
> > <mailto:dani...@grinta.net>> wrote:
> >
> >     On 06/09/23 01:27, Sagar Shankar wrote:
> >      > Hi Dan,
> >      >
> >      > Thanks a lot, this works now! A simple line on this in the pad
> >      > documentation would be great for future reference of others
> >
> >     The behavior is due to the balance directive being treated specially
> >     when sorting, not to the pad directive. Ordering is relevant for how
> >     all
> >     directives are processed. You would have observed similar issues if
> you
> >     had a transaction and a balance assertion on the same day. The order
> in
> >     which directives are processed is documented. I don't think adding a
> >     note to the documentation of each directive remembering the ordering
> >     issue would make the documentation better.
> >
> >
> > Booking decisions and validity are also order dependent.
> >
> > Given how much the current documentation emphasizes that the order of
> > entries doesn’t matter, this is IMHO confusing for new users.
>
> Can you please point to where the documentation states that ordering
> does not matter? Obviously, order matters in a system designed to track
> the changes of quantities (the balance of accounts) over time. What the
> documentation states is that the order in which the entries appear in
> the ledger does not matter, unless it is required to break ordering ties
> of events registered on the same date. This is precisely documented.
>
> > I do believe the documentation would be improved by describing
> > (somewhere) those cases where intra-day ordering *does* matter, and
> > referencing that caveat in the places where ordering-invariance is
> claimed.
>
> Ordering of transactions registered on the same day has nothing to do
> with the problem discussed in this thread.
>
> However, if you have ideas on how the documentation can be improved,
> feel free to send patches. Help is always welcome.
>

Where does the documentation live in github?  I can look again for the
spots that I personally found confusing in the past and reevaluate them
given what you've said, and if I can still think of improvements, send
patches.

Thanks,
Eric


>
> Cheers,
> Dan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/2f5012cb-2ddd-b30f-aa00-7b5bf035e7e8%40grinta.net
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAFXPr0tNJn9VHJyp2mu3FMjqpAivmep3TdB1JtxV%2B_SiXAxUXQ%40mail.gmail.com.

Reply via email to