emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Quiliro Ordóñez" <quiliro@riseup.net>
To: emacs-orgmode@gnu.org
Subject: Re: Question Regarding Creating Workflow For Automatic Formulas For Finance Based Org Spreadsheet
Date: Fri, 14 Jan 2022 11:54:45 -0800	[thread overview]
Message-ID: <5f6b2337d0d5ca303c054febba4ff8c3@riseup.net> (raw)
In-Reply-To: <b5f0fa4d-d12d-40c0-ae5c-dbf24c0eaa2e@www.fastmail.com>

El 2022-01-09 22:42, Samuel Banya escribió:
> Ah, Ledger is way too complicated for what it's worth. I've seen
> videos on YouTube about it, and every person who's praised it is
> pretty much too smart enough to be able to explain it in simple terms.

It is very easy.  I made a video for EmacsConf 2019
https://emacsconf.org/2019/talks/12/ .   I wish someone had showed me
examples like these when I started with it.  

My fiancee is a preschool teacher (programming is not her area of
expertize).  But she quickly learned how to use it.  She keeps about
3700 per year with 4500 lines.  It takes her about 10 minutes per day. 
With that investment, she can even tell how much we have spent on apples
or on all fruits (as detailed or general as she wants).  On these two
years, she has saved us about half our budget and has us living much
better thanks to the knowledge of what we want to invest on.  (We now do
not think of how to spend money, but how to invest it.  That changes the
point view completely.)
  
There are complicated reports as well as very simple ones that can be
generated.  And you can always customize them to the last bit.  There is
also a website http://plaintextaccounting.org .  There is plenty of
information there.  You can also use org-babel to include formulas for
Ledger reports.

Just ask away!  :-)


  parent reply	other threads:[~2022-01-14 19:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 16:56 Question Regarding Creating Workflow For Automatic Formulas For Finance Based Org Spreadsheet Samuel Banya
2022-01-09 19:05 ` Ken Mankoff
2022-01-09 19:48 ` John Hendy
2022-01-09 22:37 ` Neil Jerram
2022-01-10  3:42   ` Samuel Banya
2022-01-10  7:04     ` Marcin Borkowski
2022-01-10  7:17       ` Detlef Steuer
2022-01-10 15:31       ` Greg Minshall
2022-01-10 17:01         ` Samuel Banya
2022-01-10 17:23           ` John Hendy
2022-01-10 19:04           ` Marcin Borkowski
2022-01-10 22:44             ` Samuel Wales
2022-01-11  0:30             ` Samuel Banya
2022-01-11  0:41               ` John Hendy
2022-01-11  0:43                 ` Samuel Banya
2022-01-10 10:31     ` Neil Jerram
2022-01-19 15:01       ` Neil Jerram
2022-01-14 19:54     ` Quiliro Ordóñez [this message]
2022-01-16 15:15       ` Samuel Banya
2022-01-16 15:19         ` Samuel Banya
2022-01-16 15:35           ` Samuel Banya
2022-01-16 18:10             ` Eric S Fraga
2022-01-17  0:41           ` John Hendy
2022-01-10 13:35 ` Eric S Fraga
2022-01-10 17:09   ` Bob Newell

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=5f6b2337d0d5ca303c054febba4ff8c3@riseup.net \
    --to=quiliro@riseup.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).