The SQL backends will get you an instant auto-save, but only for
committed transactions. (as far as I know)
You still have to hit Enter or Tab-through to finish a transaction, at
which point the file is auto-updated. (thus, save-on-commit)
Regards,
Adrien
On 5/4/23 4:30 PM, David G. Pickett via gnucash-user wrote:
I often accidentally leave a transaction complete but with the cursor of that
sheet still on the same line, so despite an aggressive auto save setting, such
a transaction is not committed to the saved image. Of course, if it is not in
valid form, it cannot be committed! But if the host goes down or gnucash
terminates for any reason not a stable interactive exit, despite the auto save,
the entire transaction or any change is lost. I would like an option to
auto-commit such transactions, if valid, before the timed auto save.
For me, this creates loss of input when I run my nightly cron job for quotes,
where I kill any running gnucash and remove any lock to allow the quote
additions. (A side thought would to have the quote fetch built into the
interactive gnucash such that it has a way to get quotes without being killed.
Maybe a gnucash service daemon that could negotiate the updates with any
running interactive gnucash or do the updates if no interactive gnucash is
running? That in turn suggests a gnucash with a service and multiple
interactive sessions so changes in any interactive session could be notified to
other interactive sessions, supporting both quotes from a crontab scheduled
service internal or external, and multiple interactive users to support larger
enterprises.)
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
