Feature request: reload data files once changes are detected about calcurse HOT 9 OPEN

I pushed a partial solution to the pu branch. With d483407 (Do not blindly overwrite files when saving, 2017-09-07), calcurse checks whether the data files were changed before saving. If they were, you can either overwrite, cancel or run the merge tool to keep both changes.

from calcurse.

I will look into implementing an auto-reload feature as soon as possible.

from calcurse.

Thanks a bunch!

from calcurse.

I looked into it but it is a bit more involved than I thought. For example, it is not clear what to do if an appointment is deleted in the data files and the reload is triggered while the user is currently editing that appointment...

from calcurse.

from calcurse.

Discarding the editing is not a good idea because the user will be surprised. I think we should rather turn off the automatic reload temporarily during any interactive edit operations...

from calcurse.

I agree with @lfos: in normal operation check for and update changes. When editing a new appointment, todo or note, don't do that.

But then you don't cover some common synchronisation issues, which you appear to cover with your patch.

Does CalDAV accomplish the same? Or does that have disadvantages, e.g. overkill, over a solution within calcurse?

from calcurse.

I don't quite understand. How is CalDAV an alternative to reloading files once changes are detected?

from calcurse.

@randomizedthinking wanted to use calcurse at different machines and be sync'ed between them. Would CalDAV not do that (with the need of a CalDAV server, of course)?

Though even if one would accept this as a solution for synchronising between different calcurse sessions, there may be additional reasons for wanting to check for changes.

from calcurse.