Re: A feature idea: An alternative org-mode input format
On 2023-02-10, at 03:31, Alexandre Rademaker wrote: > The table would be just a normal content, right? Is the format below more > regular for org-mode? > > * [2023-01-10 Tue] Adobe Acrobat Pro >:PROPERTIES: >:ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D >:CREATED: [2023-01-25 Wed 21:40] >:END: > > | Expenses:Administrative | $33.59 | > | Equity:Admin:Somebody || > > > I am curious about the use cases for the benefits you described. Another thing you could easily do would be to use org-capture with this. Best, -- Marcin Borkowski http://mbork.pl -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/87zg9mdnu8.fsf%40mbork.pl.
Re: A feature idea: An alternative org-mode input format
Hi John, I’m a heavy user of org. This tool would be cool. Regards, Sent from my iPhone > On Feb 9, 2023, at 9:41 PM, John Wiegley wrote: > > Hi all, > > I was thinking of creating a separate tool for translating specially formatted > Org-mode files into Ledger files. For example, this entry: > >2023-01-10 Adobe Acrobat Pro >; ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D >; CREATED: [2023-01-25 Wed 21:40] >Expenses:Administrative $33.59 >Equity:Admin:Somebody > > Would be processed from this Org-mode entry: > >* [2023-01-10 Tue] Adobe Acrobat Pro > | Expenses:Administrative | $33.59 | > | Equity:Admin:Somebody || >:PROPERTIES: >:ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D >:CREATED: [2023-01-25 Wed 21:40] >:END: > > Now, why might you want to record Ledger entry in Org-mode? Because you get > these added benefits: > > - Org-mode's hierarchical organization, narrowing, searching, filtering > - Org-mode tags become Ledger tags for the whole transaction > - Org-mode properties become Ledger metadata for the whole transaction > - You can use Org-attach to attach files to entries > - You can use cross-linking to jump between entries > - You can use the agenda and calendar to review entries on given dates > > There's already a Haskell library for parsing Org-mode files, so I was > thinking that building this as a UNIX tool shouldn't be but a few days work. > It would be run as follows: > >org2ledger ledger.org | ledger -f - reg > > John > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ledger-cli+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ledger-cli/m2ilga4ofw.fsf%40newartisans.com. -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/BDD2CE96-0FA2-4CC5-8A48-588923442D4E%40gmail.com.
Re: A feature idea: An alternative org-mode input format
The table would be just a normal content, right? Is the format below more regular for org-mode? * [2023-01-10 Tue] Adobe Acrobat Pro :PROPERTIES: :ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D :CREATED: [2023-01-25 Wed 21:40] :END: | Expenses:Administrative | $33.59 | | Equity:Admin:Somebody || I am curious about the use cases for the benefits you described. Best, Alexandre > On 9 Feb 2023, at 16:40, John Wiegley wrote: > > Hi all, > > I was thinking of creating a separate tool for translating specially formatted > Org-mode files into Ledger files. For example, this entry: > >2023-01-10 Adobe Acrobat Pro >; ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D >; CREATED: [2023-01-25 Wed 21:40] >Expenses:Administrative $33.59 >Equity:Admin:Somebody > > Would be processed from this Org-mode entry: > >* [2023-01-10 Tue] Adobe Acrobat Pro > | Expenses:Administrative | $33.59 | > | Equity:Admin:Somebody || >:PROPERTIES: >:ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D >:CREATED: [2023-01-25 Wed 21:40] >:END: > > Now, why might you want to record Ledger entry in Org-mode? Because you get > these added benefits: > > - Org-mode's hierarchical organization, narrowing, searching, filtering > - Org-mode tags become Ledger tags for the whole transaction > - Org-mode properties become Ledger metadata for the whole transaction > - You can use Org-attach to attach files to entries > - You can use cross-linking to jump between entries > - You can use the agenda and calendar to review entries on given dates > > There's already a Haskell library for parsing Org-mode files, so I was > thinking that building this as a UNIX tool shouldn't be but a few days work. > It would be run as follows: > >org2ledger ledger.org | ledger -f - reg > > John > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/644327EB-51F1-44CF-8E1A-F6C1F626D27A%40gmail.com.
Re: Query Help
Thanks John! On Wednesday, February 8, 2023 at 1:08:59 PM UTC-6 John Wiegley wrote: > > "J" == Jasel17212 writes: > > J> I'm using zsh so entered: > > J> ledger reg ^exp and "(%tag1 | %tag2)" > > Sadly, it has to be more separated than this: > > > ledger reg ^exp and '(%tag1' '|' '%tag2)' > > It's a bug to me that the query parser interprets "(%tag1 | %tag2)" as if > you > had written "(%tag1 |" "%tag2)". > > John > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/62db2fbb-a89d-4e65-90fb-b8cd70b5cdabn%40googlegroups.com.
A feature idea: An alternative org-mode input format
Hi all, I was thinking of creating a separate tool for translating specially formatted Org-mode files into Ledger files. For example, this entry: 2023-01-10 Adobe Acrobat Pro ; ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D ; CREATED: [2023-01-25 Wed 21:40] Expenses:Administrative $33.59 Equity:Admin:Somebody Would be processed from this Org-mode entry: * [2023-01-10 Tue] Adobe Acrobat Pro | Expenses:Administrative | $33.59 | | Equity:Admin:Somebody || :PROPERTIES: :ID: 076497DC-45F7-43EC-BFDA-00177EFC3C0D :CREATED: [2023-01-25 Wed 21:40] :END: Now, why might you want to record Ledger entry in Org-mode? Because you get these added benefits: - Org-mode's hierarchical organization, narrowing, searching, filtering - Org-mode tags become Ledger tags for the whole transaction - Org-mode properties become Ledger metadata for the whole transaction - You can use Org-attach to attach files to entries - You can use cross-linking to jump between entries - You can use the agenda and calendar to review entries on given dates There's already a Haskell library for parsing Org-mode files, so I was thinking that building this as a UNIX tool shouldn't be but a few days work. It would be run as follows: org2ledger ledger.org | ledger -f - reg John -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/m2ilga4ofw.fsf%40newartisans.com.
Re: How to split expenses
Sorry for insist, but someone has any thoughts about the question in the end of the message below? Repeating here: But how to record when both of us paid some different amount of the same expense? Maybe this turns out to suggest to rethink the option for the case above? Below the total expense is EU 12,00 we should both pay EU 6,00, but I paid EU 10,00 and he paid only EU 2,00. Does it make sense? I am trying to record that I would add 6 to the amount he owe me, but at the same transaction, I am also removing EU 2,00 from that because he is giving EU 2,00. But I am not touching in the Liabilities:DF 2023/01/17 Place3 Expenses:Food EU 6,00 Assets:Receivable:DFEU 6,00 Assets:Receivable:DF EU -2,00 Assets:Cash EU -10,00 > On 3 Feb 2023, at 14:52, Alexandre Rademaker wrote: > > > Continuing the trip with a friend…. I renamed the accounts suggested by John > from Assets:Payable:DF to Assets:Receivable:DF. Regarding the Liabilities:DF > and Liabilities:Payable:DF. Actually Liabilities:Payable is kind of > redundant.. maybe Liabilities:DF is enough. > > when I paid something for us, I record the total cost and add in > Assets:Receivable:DF the fact that he owe me half of the expense: > > 2023/01/07 Place1 > Expenses:Food EU 6,00 > Assets:Receivable:DFEU 6,00 > Assets:Wise > > When he paid something, I recorded that I owe him half of the total. This > turned out to be the simpler alternative as Yuri's suggestion. But the > alternative in the message below is interesting too, adding a little bit of > extra complexity to move between Assets:Receivable:DF and Liabilities:DF, but > I can do that once in the end of the trip. > > 2023/01/02 Sample > Expenses:Food EU 6,00 ; total EU 12,00 > Liabilities:DF > > > But how to record when both of us paid some different amount of the same > expense? Maybe this turns out to suggest to rethink the option for the case > above? > > Below the total expense is EU 12,00 we should both pay EU 6,00, but I paid EU > 10,00 and he paid only EU 2,00. Does it make sense? I am trying to record > that I would add 6 to the amount he owe me, but at the same transaction, I am > also removing EU 2,00 from that because he is giving EU 2,00. But I am not > touching in the Liabilities:DF > > 2023/01/17 Place3 > Expenses:Food EU 6,00 > Assets:Receivable:DFEU 6,00 > Assets:Receivable:DF EU -2,00 > Assets:Cash EU -10,00 > > Best, > Alexandre > > >> On 12 Jan 2023, at 14:23, Yuri Khan wrote: >> >> On Thu, 12 Jan 2023 at 19:10, Alexandre Rademaker >> wrote: >> >>> I see your point and you are right that using the second entry below would >>> be simpler and record the fact that I owe ‘DF’ 3 euros. But using the >>> first entry below allow me to also record the total amount of the expense >>> if later on we all want to remember how much was the parking. Using only >>> the comment would be an alternative too. The only real problem with the >>> first entry is the fact that usually liabilities are negative, right? Maybe >>> I could find a better name? The ‘Payable:DF’ is to record the moneys that >>> ‘DF’ owes to me. >>> >>> 2023/01/07 Hotel Braga Parking >>>Expenses:ParkingEU 3,00 >>>Liabilities:DF EU 3,00 >>>Assets:DF EU -6,00 >> >> If you want to track everything in full detail, you can do that too. >> Just pretend that you manage all the finances. >> >> * Count goods and services you consume into Expenses. >> * Count goods and services your friends consume into >> Assets:Receivable, as if they owe you. >> * Track money you pay from the actual accounts you pay from (Assets if >> cash or debit cards; Liabilities if credit cards). >> * Track money your friends pay from Liabilities:Payable, as if you owe them. >> >> 2023-01-07 Hotel Braga Parking >>Expenses:Parking EUR 3,00 >>Assets:Receivable:DF EUR 3,00 >>Liabilities:Payable:DFEUR -6,00 >> >> At the end of trip, or at any time, you can cancel out debts: >> >> 2023-01-07 Debt cancellation >>Liabilities:Payable:DF EUR 3,00 >>Assets:Receivable:DF EUR -3,00 >> >> After the above, Assets:DF is at 0 and Liabilities:DF is at EUR -3,00, >> indicating you owe DF 3 Euro. >> >> (Unrelated: Consider using standard ISO 4217 currency codes. While we >> are at it, consider also using the standard ISO 8601 date separator.) >> > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving
