> I don't think I've encountered a situation where [a git repo of financial data] would be useful.
The repeated SHA1 commits would form a kind of semi-proof, and of course having history information would help catch and resolve data entry errors.
> I cannot imagine why I - and I spend almost all day in a `screen` session already - would want to hand-edit my transactions in a text-editor and use a CLI tool.
Ease of use. Adding a transaction is a simple 'echo … >> FILE'. Scheduled transactions are just cron jobs. You can easily write your own code to handle interesting transaction types (e.g. sum-of-years'-digits depreciation). You can easily import & export data.
If you actually live on a CLI, odds are that you actually enjoy working in your text editor.
The repeated SHA1 commits would form a kind of semi-proof, and of course having history information would help catch and resolve data entry errors.
> I cannot imagine why I - and I spend almost all day in a `screen` session already - would want to hand-edit my transactions in a text-editor and use a CLI tool.
Ease of use. Adding a transaction is a simple 'echo … >> FILE'. Scheduled transactions are just cron jobs. You can easily write your own code to handle interesting transaction types (e.g. sum-of-years'-digits depreciation). You can easily import & export data.
If you actually live on a CLI, odds are that you actually enjoy working in your text editor.