is there anything that makes it possible to read in a sources tree and create @auto nodes from it ? Do @auto nodes act like @thin (without sentinels) or more like @root ? (got to say I exclusively use @root nodes so far, maybe it's because I understand them best, can tell when to write down my changes and switch off the sentinels with @silent) But keeping a tree congruent is a pain like this and way too expensive.
Boils down to this: Could there be something like an @auto-tree to reflect a whole directory with it's changes in files and structure ? That'd be really cool. -S On 21 Jun., 12:31, "Ville M. Vainio" <[email protected]> wrote: > On Sun, Jun 21, 2009 at 11:37 AM, znafets<[email protected]> wrote: > > Maybe kind of this question got asked already but I am not aware of a > > solution that would make that problem go away. Especially when you > > guys refer to shadow nodes as "unreliable". > > Using @auto is safest when you have rapid flow of changes from other > developers. The "unreliablity" of @shadow is not much of a problem if > the underlying external file is relatively stable. > > -- > Ville M. Vainiohttp://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
