This report is somewhat related to bug 7759 and Bug 7873. (And it is in the same spirit as Bug 9283 for the Notes plugin.) It seems that Orage is unable to detect external modifications to files in ~/.local/share/orage/, especially to the orage.ics file (see Bug 7873). This is a problem when using an external program (e.g. SpiderOak) to sync Orage events between computers. What happens is that the events get saved on Computer 1, SpiderOak backs them up automatically to its servers, I close down C1, open C2, Orage opens with the _old_ version of the events, then SpiderOak on C2 checks the files on its servers and detects a newer latest version of the events, and subsequently it downloads the latest orage.ics to C2. Since Orage doesn't detect external changes, it still operates with the old events, and this is a recipe for data loss. (It can always be reverted via SpiderOak, but it gets messy.) Would you consider implementing polling for external modifications of the text files in ~/.local/share/orage/ and automatic reloading from disk of the files? Perhaps with a confirmation dialogue: 'Cancel/Keep old events', 'Reload orage.ics from disk'?
Yes, I definitely agree. This is already used for teh foreign files and should be used also for the base files.
Done in 4.9.8.0. Orage logs all noticee foreign changes ot log file. No customer visible alarms are shown. IF you are updating an appointment, which vanishes due to the external file copy, Orage gives error and does not allow update. This should happen very seldom.
(In reply to juha from comment #2) > Done in 4.9.8.0. > > Orage logs all noticee foreign changes ot log file. No customer visible > alarms are shown. > I've just tested the functionality, and it worked as expected. Really nice! I'm curious: where does Orage keep the log file?
Well....log file was bad word. Orage just writes those to terminal and when started from background those go to .xsession-errors, which is what I meant.
Fixed in 4.10.0