On Sunday, November 9, 2025 at 3:50:11 AM UTC-6 jkn wrote:

... One might expect logs like: (leaving EKR comments in)

reading settings in C:\Users\Dev\ekr.leo  # My local file, read only for 
its settings.
...
reading C:\Users\Dev\ekr.leo  # My local file, read for its entire content.

But sheesh, I appreciate this is all small beer...


Yes, it's small beer, but the question deserves a satisfactory answer. 
However, the details are subtle.

First, let me point out that every file is read independently of all others 
(iirc). For example, if (on the command line) I do:

> leo a.leo b.leo

Then Leo re-reads all settings files. It almost has to do this, except 
maybe for leoSettings.leo. But I don't know this for sure. It's only a 
guess.

Second, the title of each *tab* of Leo's window tells what local file Leo 
read to create the tab. In our example, the tabs' titles will start with 
a.leo and b.leo, with a further indication of where each .leo file resides. 
So there is no particular reason for Leo to announce (in the log) which 
local file Leo is reading, or has read. It wouldn't be *wrong* to make an 
entry in the Log, but at present Leo doesn't.

In short, I think Leo is reporting enough. But I can see that careful 
readers of Leo's log might have questions. I'm going to think further about 
this question.

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 view this discussion visit 
https://groups.google.com/d/msgid/leo-editor/def2b6ab-a1cd-494e-90b1-bab2ccb5fe65n%40googlegroups.com.

Reply via email to