On Wed, Oct 17, 2018 at 3:42 PM jkn <[email protected]> wrote: Leo doesn't continually check to see whether a .leo file has been changed. >> The workaround is not to do that. You could file an enhancement request, >> but I would reject it ;-) >> >> Given that Leo does easily (via the menu) allow you to reload a file, I > am curious what your reason for rejecting would be? >
Perhaps we are talking about different things. If you "reload" an already-loaded .leo file from the menu, Leo just switches to the outline's pane. What I am not going to consider doing is checking (continuously) to see whether you have reloaded the same .leo file from another instance of Leo. If you do that, the second instance of Leo will warn about the (one or more) .leo files already being open in the first instance of Leo. In that case, you can, and definitely should, close the second instance of Leo. If you don't, then you run the risk of making incompatible changes in the two separate instances of Leo. This is the "multiple update" problem, and Leo should not be expected to handle your confusion. Edward -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
