On Mon, Nov 10, 2008 at 10:46 AM, Kent Tenney <[EMAIL PROTECTED]> wrote:
> How about checking context to see if we are in a @shadow tree? I suppose you mean when reading and writing @shadow files. It may be possible to issue a warning. >> Context can change in a myriad of ways. Just for example, changing >> @@shadow to @shadow. > > Conversely , how about descending and searching for clones when > leaving a @shadow headline? I'm not going to try to figure out all the ways users could get themselves into trouble creating/disabling/moving clones and @shadow trees. It's totally out of the question. > If pathological situations are allowed they will occur, causing headaches > for users and support staff. True, but sometimes a warning is all that can be done. I'll consider adding a warning in the @shadow write code. 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 -~----------~----~----~----~------~----~------~--~---
