For me, i don't see very useful to assign payee to posting and not to a 
transaction.

For a transaction is an operation that happen between two person. The payee and 
the person who make his account.

In the case below, it is either not the same transaction. (So we should create 
two transactions. ) or it with the same person, so we don't need to have 
different payees. 

Moreover, i thinks i make more complex the format of the file.
Regards

Envoyé de mon iPhone

> Le 25 nov. 2016 à 19:08, Martin Blais <bl...@furius.ca> a écrit :
> 
> Can you say more about your treatment of multiple payees?
> Context:
> - If supporting multiple payees is something you guys do a lot, it should 
> probably be part of the regular Beancount syntax eventually (and its grammar).
> - I've been thinking for a long time that "payee" makes more sense as an 
> attribute of a posting instead of a transaction, but never developed this 
> idea further nor made my mind up about this. For instance, a syntax like this 
> might be more convenient to provide multiple payees:
> 
>    2016-11-24 * "Shuttle to Hotel"
>      "Fly Shuttle"   Expenses:Transportation:Bus    25.00 USD
>      "Surfjack hotel"  Expenses:Accommodation:Tips   3.00 USD  ;; Porteur
>      Assets:Cash
> 
> 
> 
> 
> 
> 
> 
>> On Fri, Nov 25, 2016 at 7:15 AM, Jakob Schnitzer <notificati...@github.com> 
>> wrote:
>> We could actually get around this problem by changing this filter to a 
>> regular expression. This would make it much more powerful IMHO. Filtering 
>> for a single payee would behave the same way, filtering for a few, say two 
>> or three, would be a bit more cumbersome but filtering for a whole class, 
>> say everything with "restaurant", would then be possible. What do you think?
>> 
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub, or mute the thread.
>> 
> 
> -- 
> 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 post to this group, send email to beancount@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beancount/CAK21%2BhNm3rBELm0zHkn-atuZeGcGiSHR58ANtTrL_SHW5HRhwA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/F4E33AAA-EEC2-40CA-8457-94ED48D0A61B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to