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 <[email protected]> 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ledger-cli/644327EB-51F1-44CF-8E1A-F6C1F626D27A%40gmail.com.
