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: Mon, 10 Jan 2022 10:31:51 +0000	[thread overview]
Message-ID: <CAKuG=vt4Ds3XfjGfkVuNDcUUD80Z7hfK+rjFPAbakPAtjEk44Q@mail.gmail.com> (raw)
In-Reply-To: <b5f0fa4d-d12d-40c0-ae5c-dbf24c0eaa2e@www.fastmail.com>

On Mon, 10 Jan 2022 at 03:42, Samuel Banya <sbanya@fastmail.com> wrote:
>
> 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.

I have similar observations.  I don't (so far) see that Ledger (or
alternatives) offers enough added value to be worth incorporating in
my workflow, compared to directly processing the raw data.

The value that would be of interest to me is:
- Classifying/grouping transactions at analysis time (not entry time)
according to a set of rules/regexps etc.
- Drawing insights by analysing past expenditure, with that kind of
classification.
- Using such insights as part of future budgeting.
- An overall functional approach, where the raw data is never changed,
and the other inputs to an analysis can be tweaked on each run.

I wish plaintextaccounting.org had a forum/ML for discussing this kind
of thing, as it isn't specific to any of ledger/hledger/beancount in
particular.

Best wishes,
    Neil


  parent reply	other threads:[~2022-01-10 10:33 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 [this message]
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=vt4Ds3XfjGfkVuNDcUUD80Z7hfK+rjFPAbakPAtjEk44Q@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).