I wonder if I could sneak a feature request in here? I am often guilty of having files open on different machines and ending up with different versions - in terror of losing some useful piece of info - I would like a 'merge' option that saves all nodes from the two different files into one file - happy for it to be under a new name. Where individual nodes have been altered save them both.
ta IH On Monday, 17 September 2018 10:41:04 UTC+1, jkn wrote: > > Hi all > I'm trying to understand whether Leo has the ability to reload a file > that has been changed from under its feet, as it were. > > Background: I run Owncloud on some of my PCs, where a change to one file > gets propagated to the others. This might include some .leo files. > > If I am working on a file and it gets changed via owncloud, I would like > the new file to be loaded by Leo - either automatically, or perhaps with a > prompt. This 'auto-reload' is how my other editor works, and it works well > for me like this. > > From the prompts I get, and a little investigation (LeoExternalFiles.py) > it seems that Leo wants to work the other way round - it can tell that the > file has changed, but asks me to to confirm an overwrite to the updated > file on disk. > > This could also be a useful way of working, I appreciate; but is there a > way of having the new file on disk take precedence? > > Thanks > Jon N > -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
