Dear all,
is there a profound reason (which I'm clearly missing) why #tags can be
attached to a transaction as a whole, but not to individual postings?
It seems to me that, conceptually, if metadata are allowed to be both
transaction-global and posting-specific, so should #tags.
There are two workarounds for this that I can see:
- use None-valued metadata, e.g.,
2014-05-05 txn "Cafe Mogador" "Lamb tagine with wine"
Liabilities:CreditCard:CapitalOne -37.45 USD
tag1:
tag2:
Expenses:Restaurant
- use metadata entries that contain tags as values:
2014-05-05 txn "Cafe Mogador" "Lamb tagine with wine"
Liabilities:CreditCard:CapitalOne -37.45 USD
tags: #tag
Expenses:Restaurant
with the additional caveat that only one tag seems to be allowed as
metadata value, so it's cumbersome to add multiple tags this way.
Is this SMOP (and if so I'll be happy to file a ticket), or am I missing
something more profound here?
Many thanks in advance,
Cheers.
--
Stefano Zacchiroli . [email protected] . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader . OSI Board Director . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/20161103180709.5vte7xolyi5hwtwv%40upsilon.cc.
For more options, visit https://groups.google.com/d/optout.
