On Fri, Feb 27, 2009 at 3:11 PM, Peter Bienstman <[email protected]> wrote: > > On Feb 26, 8:06 pm, "Edward K. Ream" <[email protected]> wrote: >> To put it another way, the challenge is to put structure in the .leo file, >> while putting content in the external files. This seems impossible, in >> general. The closest general solution seems to be @shadow. Eliminating >> public sentinels would seem to require @shadow. I'm uncomfortable with >> that, but maybe it's just discomfort. > > Is there an obvious and frequently occurring use case where it would > be impossible to use @shadow?
I forget, can the @shadow shadow directories be placed somewhere other than under the directory containing the file? If not, creating directories within the tree would be considered 'pollution' by many, especially if being versioned and/or shared. > > If that is not the case, I'd remove the other ways of managing > external files from the documentation, so as not to confuse new users. > > (And should @shadow become some sort of default, that brings me back > to the motives underlying my older post here: > http://groups.google.com/group/leo-editor/browse_thread/thread/21e4a44519def04b/0e61c2d25c3c8f14#0e61c2d25c3c8f14 > ) > > Peter > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
