and so on. then i include accountnames.ledger in my main ledger file. The hope was that buchhaltung would use these to seed TAB-autocompletion in match or add. However, it seems it does not.
Then, I tried to workaround this by generating a bogus transaction with each of these accounts involved at 0 EUR for each account, and put this on top of the import-ledger. Again, buchhaltung did not pick it up as autocompletion targets ….
I believe it’d be way more convenient for users who prefer a fixed list of pre-defined accounts to seed auto-completion like this. It also makes accidentally entering invalid or typo-ed accounts less likely.
I created a
accountnames.ledger
containing a list of statements like:and so on. then i
include accountnames.ledger
in my main ledger file. The hope was thatbuchhaltung
would use these to seed TAB-autocompletion inmatch
oradd
. However, it seems it does not.Then, I tried to workaround this by generating a bogus transaction with each of these accounts involved at
0 EUR
for each account, and put this on top of the import-ledger. Again,buchhaltung
did not pick it up as autocompletion targets ….I believe it’d be way more convenient for users who prefer a fixed list of pre-defined accounts to seed auto-completion like this. It also makes accidentally entering invalid or typo-ed accounts less likely.
Nevertheless, thanks for your great tool ^_^