On 12/13/2013 2:59 PM, SegundoBob wrote:
I couldn't find any documentation from which I could infer that all
settings must reside in a .leo file not an @file, @edit, etc. There
may be such documentation. I have no opinion about whether or not
there should be such documentation.
Experimentally, I determined that this restriction exists. No errors
or warning messages are caused, but the settings in an @file file are
simply ignored--so far as I can tell.
I tried two cases:
Case 1:
@file x.txt
@settings
Case 2:
@settings
@file x.txt
It may well be too hard and messy to relax this restriction. I wanted
to put my settings in an @file file to obtain easier to comprehend
differences from my source control system.
I believe this is because @settings nodes have to be a top-level node.
They're not top-level if they're beneath a @file node!
But you're right, perhaps this should be relaxed a bit... I can see the
benefits. But how to handle conflicts, i.e. two @file nodes have
different @settings nodes containing different values for the same
setting? My first thought would be that the last setting that Leo reads
wins.
-->Jake
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
