On 12/11/2013 7:05 AM, Edward K. Ream wrote:
In general, when two programs have copies of the same data, the last
program to write the data wins. There is no way around this with
present file systems.
True, but there is a very simple way to alleviate the issue: when
loading/saving the file, store a modification time. Then use an idle
hook in the background to check the file on disk's modification time --
if it's newer than the cached version, pop up a dialog informing the
user and ask them if they would like to reload.
The majority of other editors I've used in the past do this: Editra,
gedit, geany, kate, sublime (apparently), etc.
It's a fantastically easy way to prevent un-informed data loss. The user
is explicitly made aware that a conflict has arisen, and given the
option of which data to keep.
-->Jake
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
