Simon Michael

> "retroactively added transactions" - is "non-date-ordered transactions" an equivalent way of saying it ? PS another problem case is records which are date-ordered but not stably-ordered, ie the relative...

Thanks for the comments. Some more: > > "retroactively added transactions" - is "non-date-ordered transactions" an equivalent way of saying it ? > > If "non-date-ordered transactions" means "a set...

Now that I've toiled over this, I'm not sure if it's the best idea. I expect this to be a usability improvement and not problematic in practice. But any apparent...

Some alternatives.. 1. Keep the status quo. If you use `--infer-equity` and `check accounts`, you must add the two account declarations required for each commodity pair you exchange. Possibly make...

> What about providing a way to "declare" arbitrary subaccounts of a given account? I am interested in things like this too. I haven't had a clear idea that seemed...

Here is [related discussion on the mail list](https://groups.google.com/g/hledger/c/3ladlRTRKIg/m/T2r022BkAAAJ). I started this thinking it was a small tweak but it turned out to be bigger than expected. I think this exception...

> So in the end we're strengthening check accounts, not weakening it. Correction, disregard that comment. We're keeping check accounts strong, as it was before. No change to check accounts.

I think I was confused, assuming that space-separated terms inside a boolean query were combined with AND; they're not. I have fixed/expanded the doc at https://hledger.org/dev/hledger.html#boolean-queries and suggested avoiding space-separated...

If anyone thinks we should disallow space-separated terms inside boolean queries to reduce confusion, let me know.

Good catch @paulnice - now fixed in hledger master.