Mykola Orliuk

I was concerned about old behaviour because it basically produce result that might be confusing when tag name and value may form string that matches account name. I prefer to...

If we want to make `monthly` to be day-agnostic. Then we probably should have behaviour like: `monthly from 2017/1/5`: gives dates `2017/1/5`, `2017/2/1`, `2017/3/1` ....

@hledgerlist , you are right I'm refering to `splitSpan` used in multi-period reports. Ideally we should specify `monthly from 2017/1`. I see that it makes rendering of column headers much...

And I gues current behavior is definitely more useful in terms of "I want to see week report that includes that days" (`hledger bal -p 'weekly in today'`).

I didn't found in [documentation](http://hledger.org/manual.html#period-expressions) any mention about extending ranges to include complete periods. The only place is code documentation for `splitSpan`: ```hledger -- | Split a DateSpan into one...

Aliases actually propagated to included files. Since migration to hledger I changed my layout to something like: ```ledger # effective-hledger.dat commodity $ ; note American Dollars format $1,000,000,000.00 alias tips=Expenses:Tips...

I miss that feature only for merging multiple journals. Example: I have some balance assertions/assignments from bank account in one journal and automatic export of expenses on my shop account...

I also got a use-case for it to track traffic KB/MB/GB/etc... Probably we still need `commodity` directive to have default representation. But on the other hand it is completely useless...

@simonmichael, do you mean that we can require something like: ```ledger commodity 1,000,000,000 B unit 1.0 KB = 1024 B ; inherits base but overrides for KB precision unit 1.000...

@mahmoodw, thank for keeping an eye on stale issues. I think, this one is just waiting for ROCm 6.2. But that doesn't mean that issue no longer exists. On NixOS...