From: "Samuel Banya" <sbanya@fastmail.com>
To: "Greg Minshall" <minshall@umich.edu>,
"Marcin Borkowski" <mbork@mbork.pl>
Cc: Neil Jerram <neiljerram@gmail.com>,
Charles Berry <emacs-orgmode@gnu.org>
Subject: Re: Question Regarding Creating Workflow For Automatic Formulas For Finance Based Org Spreadsheet
Date: Mon, 10 Jan 2022 12:01:35 -0500 [thread overview]
Message-ID: <e64ebfe3-6d33-489e-9c95-bc3313027d18@www.fastmail.com> (raw)
In-Reply-To: <2352934.1641828705@apollo2.minshall.org>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
The 'double reporting' idea might have been why I just flat out shook my head when I saw the one presentation on 'ledger' in Emacs on YouTube a while ago as its a bit too complicated and unnecessary for a layman.
I just don't need that kind of over-thinking when it comes to my finances since I just need a spreadsheet that listed expenses, and to count totals. That's about it.
I will take a look at the other suggestions with specific Org Mode formulas, looked awesome, thanks.
On Mon, Jan 10, 2022, at 10:31 AM, Greg Minshall wrote:
> > I'm wondering if your opinion about Ledger isn't influenced by the fact
> > that it uses basic accounting principles, like the idea of double-entry
> > accounting. For me, it's /very/ simple and intuitive, but I graduated
> > in economics many years ago and had a (basic, but still) course on
> > accounting. If that is your problem, I'd suggest spending some time on
> > understanding that - even if you don't end up using Ledger but some
> > other software, you might find learning about accounting useful. (Also,
> > it's fascinating. No, really! It's an extremely clever abstract
> > system with a real-life use-case.)
>
> i agree that learning the principles of double-entry is worthwhile,
> actually interesting, and of a very interesting history!
>
[-- Attachment #2: Type: text/html, Size: 1817 bytes --]
next prev parent reply other threads:[~2022-01-10 17:08 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 [this message]
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
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=e64ebfe3-6d33-489e-9c95-bc3313027d18@www.fastmail.com \
--to=sbanya@fastmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
--cc=minshall@umich.edu \
--cc=neiljerram@gmail.com \
/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).