Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: colindean/plaintextaccounting_workshop
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2020.07.24.0
Choose a base ref
...
head repository: colindean/plaintextaccounting_workshop
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
  • 3 commits
  • 3 files changed
  • 2 contributors

Commits on Jul 24, 2020

  1. Copy the full SHA
    3d4a52f View commit details
  2. Copy the full SHA
    c33f360 View commit details

Commits on Apr 27, 2021

  1. Copy the full SHA
    dede19a View commit details
Showing with 19 additions and 5 deletions.
  1. +7 −0 0600_ledger-autosync.md
  2. +3 −2 0700_fava.md
  3. +9 −3 README.md
7 changes: 7 additions & 0 deletions 0600_ledger-autosync.md
Original file line number Diff line number Diff line change
@@ -93,6 +93,13 @@ ledger-autosync \

If you run @lst:export_append again, you'll notice that nothing else new was added! `ledger-autosync` successfully used the CSVID it generated to keep from adding transactions it already had converted.

## Rules to keep in mind for synchronizing

1. Synchronize your primary account first.
2. Synchronize transfer or payment IDs from subsequent accounts that have transfers or payments to or from that primary account _before_ mixing in the other accounts' full records. This ensures that you are tracking both records' IDs in order to prevent duplicate entries. You can _manually_ delete the transfer or payment transactions from your initial conversion against your primary ledger file or you can re-run `ledger-autosync` and it will ignore the IDs that are already present in the ledger file passed as `--ledger`.
3. Diligently use `; AutosyncPayee: XXX` tags in transactions where you modify the payee. This will enable `ledger-autosync` to find transactions and set the counter-transaction (the expense, generally) automatically. This will save you literally hours of data entry per update session!
4. Use your editor's autocomplete functionality. [`vim-ledger`](https://github.com/ledger/vim-ledger) lends itself to this with its `Ctrl-X Ctrl-O` autocompletion trigger while in insert mode: it'll look at all account names in the current file by doing `ledger -f - accounts` and build suggestions based on partial matches. `E:E:B` could expand to `Expenses:Electronics:Batteries`. Look how much time that saves in typing alone!

## Converting with `ledger`

Importing with `ledger` is possible through its `convert` command.
5 changes: 3 additions & 2 deletions 0700_fava.md
Original file line number Diff line number Diff line change
@@ -56,9 +56,10 @@ L2B_CONFIG = scripts/ledger2beancount.yml

BEANCOUNT_FILE=reports/$(LEDGER_FILE).beancount

beancount: $(BEANCOUNT_FILE)
.PHONY: beancount
beancount: $(BEANCOUNT_FILE) ## creates a beancount version of the ledger file

fava: $(BEANCOUNT_FILE)
fava: $(BEANCOUNT_FILE) ## runs fava on the beancount version of the ledger file
fava $(<)

$(BEANCOUNT_FILE): $(LEDGER_FILE) $(L2B_CONFIG)
12 changes: 9 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,19 @@
# Plain Text Accounting Workshop

:warning: **This is under active and heavy development.** :warning:
:warning: :warning:
If you're wanting to follow the workshop,
download the PDF (or the HTML) and the tar.gz from the
[releases page](https://github.com/colindean/plaintextaccounting_workshop/releases/latest).

If you're reading the this README on the linked repo, you're not reading the right thing:
the instructions below are for _building_ the workshop distributable files.

## Contributing to the Workshop

The Markdown files in this directory are [`pandoc`-flavored
Markdown](https://pandoc.org) so they may not correctly render on GitHub. This
is especially true of the tables.

## Contributing

Run `brew bundle` to install the easily available dependencies to build this
workshop document.