I've wondered about this, too.  It seems obvious to me that if LeoPyRef has 
been changed outside of the Leo session that Leo should restart.  This 
could happen, e.g., if the user checks out a different branch of leo-editor 
or updates the current branch.  For other outlines, maybe the thinking was 
that any outline might contain some part of Leo's runtime code, but if that 
every was the case it doesn't seem so any more.

On Wednesday, June 28, 2023 at 11:49:08 PM UTC-4 Félix wrote:

> Exactly as per the subject line, I'm wondering why does Leo asks to 
> restart when a .leo file modification is detected? Instead of asking to 
> reload the file?
>
> I feel like I asked this question in the past and I cant remember the 
> reason, ...but I searched this google-group for 'restart' and I couldn't 
> find anything... so i just posted this
>
> Thanks for anyone who can enlighten me about this :)
>
> Félix
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/bfe87353-308b-4a56-ac18-673b979dae08n%40googlegroups.com.

Reply via email to