emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neil Jerram <neiljerram@gmail.com>
To: Samuel Banya <sbanya@fastmail.com>
Cc: Charles Berry <emacs-orgmode@gnu.org>
Subject: Re: Question Regarding Creating Workflow For Automatic Formulas For Finance Based Org Spreadsheet
Date: Sun, 9 Jan 2022 22:37:26 +0000	[thread overview]
Message-ID: <CAKuG=vtQ=1iPtpQ+mhD4-4K+x4afMOLUPW-fqzugHAe5=Qe4SA@mail.gmail.com> (raw)
In-Reply-To: <137562d1-e6fe-4a68-b18b-abedef513fbd@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Sun, 9 Jan 2022, 17:18 Samuel Banya, <sbanya@fastmail.com> wrote:

> Hey there,
>
> So I've been managing my finances via an org doc that basically has tables
> that list all the expenses from my bank account, which has been awesome on
> some respects.
>

I also save and process my bank account transactions with Org, and I agree
that it's awesome.  The bank's own website and analysis capabilities are
rubbish in comparison.

For what it's worth, my approach is:

- Periodically download transactions when available (in OFX format, but
that's not important).

- Use Org and Babel with Scheme code to run arbitrary analyses over those,
with the results displayed in Org tables.

- Sometimes there are cases when I need an additional computation on one of
the output tables, and I can do that with an Org spreadsheet formula.  But
if it was anything useful in the longer term, I'd add the logic to the
Scheme coding instead.

So I'd agree with the response that this kind of thing is a bit too complex
for Org table formulas alone.

Best wishes,
     Neil

>
>

[-- Attachment #2: Type: text/html, Size: 1970 bytes --]

  parent reply	other threads:[~2022-01-09 22:38 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 [this message]
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
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='CAKuG=vtQ=1iPtpQ+mhD4-4K+x4afMOLUPW-fqzugHAe5=Qe4SA@mail.gmail.com' \
    --to=neiljerram@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sbanya@fastmail.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).