Re: @clean nodes stopped updating

Thanks for figuring this out! That did indeed fix it on my Mac. On Windows I'm using 5.3 (was not able to get anything else to work, will write separate post) and this doesn't seem to be a problem with that one. I think not having this be the default is pretty dangerous. I clobbered some

Re: @clean nodes stopped updating

> > I'm dithering about @bool check_for_changed_external_files. On the one > hand, it seems unreasonable not to enable it by default. It's the expected > behavior for most editors and IDE's. Otoh, there are rare performance > problems with network drives.​ > Is it possible for Leo to

Re: @clean nodes stopped updating

> > ​I would have done something similar. But you don't have to use a temp > folder​. You can do the git bisect "in place", in your normal leo-editor > folder. When you are done, git will leave your folder just as it was. > > Edward > Yes, I knew it would, but in my Leo folder there are

Re: @clean nodes stopped updating

On Wed, Apr 12, 2017 at 5:20 AM, Edward K. Ream wrote: Rev 0fb4cec improves traces and comments to make clear to me and future > maintainers what is happening. > ​I had a lovely morning walk today, watching the crew teams train on Lake Mendota. At the end of the walk I

Re: @clean nodes stopped updating

On Wednesday, April 12, 2017 at 4:17:12 AM UTC-5, Edward K. Ream wrote: > > > I have bisected and found that the culprit is change in default setting. > ... > > Just add @bool check_for_changed_external_files = True to > myLeoSettings.leo > @Joe Orr: Please report any further problems you might

Re: @clean nodes stopped updating

> I have bisected and found that the culprit is change in default setting. ... > Just add @bool check_for_changed_external_files = True to myLeoSettings.leo Excellent sleuthing. Thank you Vitalije. Edward -- You received this message because you are subscribed to the Google Groups

Re: @clean nodes stopped updating

Just add : @bool check_for_changed_external_files = True to myLeoSettings.leo in your configuration file. Vitalije -- 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

Re: @clean nodes stopped updating

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 Date: Fri Dec 16 15:06:40 2016 -0500

Re: @clean nodes stopped updating

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

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 3:34:35 PM UTC-5, Edward K. Ream wrote: As I noted in #472 , > everything works for me on Windows. So this is the typical long-distance > debugging mystery. Here are my suggestions. > And here are a few more:

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 3:34:35 PM UTC-5, Edward K. Ream wrote: > > On Tuesday, April 11, 2017 at 10:36:30 AM UTC-5, Edward K. Ream wrote: > > > I'll attempt a fix later today. > > As I noted in #472 , > everything works for me on

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 10:36:30 AM UTC-5, Edward K. Ream wrote: > I'll attempt a fix later today. As I noted in #472 , everything works for me on Windows. So this is the typical long-distance debugging mystery. Here are my

Re: @clean nodes stopped updating

On Tuesday, April 11, 2017 at 5:08:58 AM UTC-5, Edward K. Ream wrote: > Please file a bug report here Never mind. I just created #472

Re: @clean nodes stopped updating

On Tue, Apr 11, 2017 at 4:59 AM, Joe Orr wrote: > I tried rolling back to the commit before b7638799d6, no luck. > > In fact, now it is worse, when I make a change in Webstorm and then go to > Leo, not only is there no warning, any changes I then make via Leo clobber > the

Re: @clean nodes stopped updating

I tried rolling back to the commit before b7638799d6, no luck. In fact, now it is worse, when I make a change in Webstorm and then go to Leo, not only is there no warning, any changes I then make via Leo clobber the Webstorm file with no warning. And it is still doing this after I reset to the

Re: @clean nodes stopped updating

I am not certain but it could be caused with the fixing of other bug I have reported recently in checkTimeStamp method. It used to report non-existing files in some cases as changed and to fix that the above method was changed to return True by default which means "file not changed". Try to

@clean nodes stopped updating

I'm going back and forth between Leo and Webstorm. Until today, when I made a change in a @clean file in Webstorm, Leo would pop up a message saying that the file has been changed and update its copy. That just stopped happening. Now Leo doesn't update the node unless I close and open the Leo