Following up on Kent's prizel. We could create a Leo repository now.
In another post I discussed this possibility:: - @file x.leo - @file y.leo etc. This morning I realized we could have the same thing, just by defining leo.leo something like this:: - Notes - @file leoNotes.txt - Core < same as Code tree in leoPy.leo> - Plugins < contents of LeoPlugins.leo> - Dist @file leoDist.leo - Docs <contents of LeoDocs.leo> Or something like this. The point is that we don't need new invention to create "grand unified Leo base." However, there is a real tension between one .leo file and many. Pluses of leo.leo: - easier global searches. Minuses of leo.leo: - all files *always* get loaded, so slower startup. - Less separation, which can be dangerous. - Less flexibility in loading, but maybe not so important. Your comments please. Would a single leo.leo be a good idea? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
