fava icon indicating copy to clipboard operation
fava copied to clipboard

Transaction inserting: Support adding per-posting metadata

Open pmarciniak opened this issue 4 years ago • 4 comments

When entering transactions directly from a text editor, I often add comments to postings, e.g.:

1955-11-05 * "" "Grocery shopping" [...] Expenses:Groceries:Alcohol 20.00 USD memo: "Beer for the BBQ" [...]

This is currently not supported in fava's transaction adding dialog.

pmarciniak avatar Aug 29 '20 16:08 pmarciniak

I don't really intend for the transaction form to support every intricacy of Beancount's syntax. At some point, I don't think there's much to be gained and writing the transaction directly in the editor would be similarly convenient.

yagebu avatar Oct 02 '20 15:10 yagebu

Is this something you would accept a pr for or are you certain you don't want this? (same question for #1148)

Don't want someone wasting their time tackling an issue that will not be approved.

mcbloch avatar Nov 04 '20 14:11 mcbloch

OK, just for posterity, here's why I think entering transactions directly in the editor is far less convenient. This applies especially when one manually enters transactions from receipts, so dozens of transactions during a single session, and every second/click/keystroke/fava UI refresh counts:

  1. One cannot rely on "insert-entry" fava-option and has to manually pick one out of potentially dozens of files to enter the transaction into.
  2. No auto-completion of the Payee name
  3. No pre-populated transaction template after choosing an already used Payee
  4. No auto-formatting: indentations need to be added and removed manually, values not automatically aligned to the right.
  5. No way to have simple arithmetic done and skip the main currency symbol. I.e. when entering with the dialog, I can write simply "2.20+3.30" and have "5.50 CHF" end up in my beancount file.

pmarciniak avatar Nov 22 '20 13:11 pmarciniak

here's why I think entering transactions directly in the editor is far less convenient.

I hear you - there's definitely aspects where the transaction form excels :) I mostly use a two-step process, because I find certain edits to be faster in a proper editor like vim, so I can also do edits there that the transaction form doesn't allow.

I personally have no real use for it but I wouldn't be completely opposed to it either. But I think an implementation should make some smart use of something like keyboard shortcuts so that we don't have to add a ton of buttons.

yagebu avatar Nov 22 '20 18:11 yagebu

This was added in #1722

yagebu avatar Jan 20 '24 10:01 yagebu