I have bisected and found that the culprit is change in default setting.
Here is relevant commit:
2a0eca1635457b379e6e1cbfab6595e55afbd635 is the first bad commit
commit 2a0eca1635457b379e6e1cbfab6595e55afbd635
Author: Edward K. Ream <[email protected]>
Date: Fri Dec 16 15:06:40 2016 -0500
Set @bool check_for_changed_external_files = False by default, and
reference #262,
@bool check_for_changed_external_files may hang on network files.
Leo build: 20161216150641
:040000 040000 a946721dce8ae22363024fd5eedd9caea780e930
81c2141e6c4404f6dab63b3d93971e9d7f930551 M leo
On Tuesday, April 11, 2017 at 10:45:23 PM UTC+2, Edward K. Ream wrote:
>
> On Tuesday, April 11, 2017 at 3:40:38 PM UTC-5, Edward K. Ream wrote:
>
> > HTH. We'll get to the bottom of this.
>
> And be sure to verify that your tool chain is actually updating the files
> you think it is.
>
> The symptom that you must reload Leo to see changed files is quite
> strange. It argues that your tool chain *is* updating files, but we have
> to check everything.
>
> We have to run Leo in a console so we can see all exceptions, especially
> uncaught exceptions.
>
> For sure something strange is going on. A silently hidden exception, an
> invisible popup, files not actually being saved, on_idle checks not
> happening at all...
>
> 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.
