Simon Michael

Thanks for the discussion and PR, and sorry for the slow response. After looking into it.. yes, though docs don't explain it well, tags are multi-valued; they collect and add...

PS re this example: > ``` > ❯ hledger -f book.hledger register tag:concerns=me --pivot=concerns > 2022-11-17 Aldi me -30 € -30 € > me 20 € -10 € > you...

I have clarified the current behaviour at https://hledger.org/dev/hledger.html#tag-values, for a start.

I don't think options for this will be worth their cost - better if we can figure out and provide the best default behaviour, and if necessary document workarounds..

It's true that children can't remove tags inherited from parents, but maybe that's for the best ? If not, we should have some examples of real-world situations which need this...

Re that example: I see what you mean, but it's not very compelling because you could simply do: ``` 2022-12-21 Today's work Work:A 3h Work:A 2h Work:A 1h Work:B 1h...

Should `print --all-tags` or `print --explicit-tags` show all inherited/acquired tags on the transaction and postings ?

Tags are - "inherited downward" - from accounts to subaccounts - from accounts to postings - from transactions to postings - "acquired upward" - from postings to transactions In the...

I don't think the sample size is large enough; no-one on the list has responded yet. I am personally against adding syntax for multiple tag behaviours as I said.

These are things that would help this to move forward, I think: 1. Several persuasive realistic examples of need gathered in one place 2. > In the https://github.com/simonmichael/hledger/pull/1955 PR, tests...