From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org and ledger
Date: Fri, 31 Oct 2014 11:56:51 -0700 [thread overview]
Message-ID: <87y4rwysng.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 4AA4F46C-5ABD-481A-8F95-2401FC407E03@agrarianresearch.org
Vikas Rawal <vikaslists@agrarianresearch.org> writes:
> I have started using ledger with Org, and would be interested in knowing experiences of other users.
>
> I see two sets of uses in combining Ledger with Org.
>
> 1. Record keeping of transactions: Org works with ledger mainly
> through babel. Has anyone considered the possibility of maintaining
> the records natively in Org, which could be exported to ledger?
> Keeping native ledger source blocks in Org does not seem to add much
> value as far as maintaining books is concerned. Some people have tried
> some basic expense recording in Org, but to my knowledge, these
> solutions do not talk to ledger.
I've certainly thought about it :)
I think the ideal solution for me would be org headings with
ledger-specific properties. So you could have date and payee properties
(defaulting to using the heading text and any timestamp present), and
then as many LEDGER_POSTING properties as you like. You could "export" a
subtree of postings to a real ledger file, and there would be an
export-and-archive command that would "permanently retire" a set of org
headings as a ledger file.
When keeping track of payments I need to make, or need to receive, the
duplication of data in my org and ledger files has always annoyed me.
I haven't actually done anything about it, though :)
> 2. Generating reports: Babel results do not use the standard Org table
> syntax. Given my limited knowledge of lisp, I am finding it difficult
> to programme customising these reports in Org. It would be of much
> benefit if other users could share how they customise ledger reports
> in Org. Some examples would be great.
Can't help here, sorry.
next prev parent reply other threads:[~2014-10-31 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 7:02 Org and ledger Vikas Rawal
2014-10-31 18:56 ` Eric Abrahamsen [this message]
2014-11-03 16:32 ` Eric S Fraga
2014-11-06 17:27 ` Alan Schmitt
2014-11-07 13:19 ` Sharon Kimble
2014-11-07 13:36 ` Eric Abrahamsen
2014-11-07 19:53 ` Sharon Kimble
2014-11-08 15:45 ` Eric S Fraga
2014-11-10 7:37 ` Eric S Fraga
2014-11-07 18:51 ` Eric S Fraga
2014-11-09 4:34 ` Daniel Clemente
2014-11-09 13:29 ` Eric S Fraga
2014-11-10 7:08 ` Bernhard Pröll
2014-11-10 9:08 ` Daniel Clemente
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 18:01 [ANN] Org Invoice 1.0.0 Peter Jones
2008-12-06 19:36 ` Mark A. Hershberger
2008-12-06 21:34 ` Peter Jones
2008-12-07 20:23 ` Mark A. Hershberger
2008-12-07 22:25 ` Org and Ledger (was: Re: [ANN] Org Invoice 1.0.0) Carsten Dominik
2008-12-08 16:58 ` Org and Ledger Mark A. Hershberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4rwysng.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).