On Fri, 27 Feb 2009 11:39:42 -0600 "Edward K. Ream" <[email protected]> wrote:
> @shadow is *not* a collaborative @<file> type, so it can not be made > the basis of any unified @file scheme. Ironically, @shadow now seems > almost useless. The only reason that comes to mind for using @shadow > is to be able to publish source code without sentinels. But Leo > already has a remove-sentinels command. @shadow is my favorite at-file type :-b :-) I like to look at diffs of my own work, so I can tell whether I did only what I intended and no more (i.e. did I remove all debugging code etc.) I do not want to see sentinel poop in my diffs. So I must use @auto or @shadow. Unlike @auto, @shadow lets me use organizer nodes etc. And I would use @shadow in a collaborative setting if it cleanly degrades to @auto when it can't work out what happened to the file. I lose my organizer nodes, but that's ok. Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
