On Thu, Mar 12, 2009 at 11:07 AM, Edward K. Ream <[email protected]> wrote: > > > > On Mar 12, 10:53 am, "Ville M. Vainio" <[email protected]> wrote: > >> I think the key here is using @shadow. Do not try to fix @auto :-) > > Actually, using @shadow does make sense in a sprint, for example. In > many situations, including sprints, we can assume that only one pair > of people will be working on a file at once. In this "controlled" > collaborative environments, @shadow will work fine. �...@shadow will not > work so well when several teams are working on the same file at the > same time.
I don't understand these implications, as I remember, @auto is more 'pure' than @shadow because @shadow must create a .shadow directory next to any external files it has loaded. If @shadow could use it's own directory structure, away from the external files, I'm not clear how it's different from @auto from the user/collaboration standpoint. > >> You can store the information of "bad" lines in shadow files, so the >> user never sees that stuff. > > Probably true for most lines. However, the problems I was discussing > happen when a line can not be represented (or disambiguated) properly > by @thin, say. > I'll say more in a reply to myself. > > Edward >> >> -- >> 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 -~----------~----~----~----~------~----~------~--~---
