On Fri, Nov 1, 2013 at 10:31 AM, Kent Tenney <kten...@gmail.com> wrote:
> It seems this is a one-off solution, It's a customized solution, for a particular application. > would require always starting > with a copy of the provided customized file, made more fragile > by a hidden startup node. > The startup node, with customized settings, is more robust (for the app) because of the @settings node provided *for that particular file*. > Are there limitations to settings which prevent a special myLeoSettings.leo > file from providing the customizations? No, it works like any .leo file (to the first approximation ;-) > If not, it seems simpler and more > robust for each newly created Leo file to be optimized. > Well, it's a matter of opinion. One person might have several .leo files, each customized in a different way. But nothing prevents someone from copying settings from the customized .leo file to myLeoSettings.leo. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
