Isn't @shadow really a sort of extension to what diff does? Just geared to deal with structure? And with inherent imperfections just as diff has?
You'd be giving Leo users a "special diff" that gives them a perhaps manual workaround process, while wiring right into the vcs. It would sort of sell the idea that some people are doing this cool outlining of code, with a diff-like facility to help them incorporate with "legacy" vcs'es that don't yet have that consideration built into them. People with Leo do fun stuff, committing @file outputs right into the vcs, just having to work around on those probably occasional times when they haven't "reserved" the doc and somebody else has changed so much they can't easily @shadow, so Leo's telling them so they can then deal with it as necessary. Probably you'd end up with other people saying wow that's cool, and yeah that's a pain what you have to do but I can see why that outlining stuff is cool, so maybe ... hmm . . . we might think about adapting the cvs . . . :-) Seth On Wed, Dec 11, 2013 at 7:45 PM, Seth Johnson <[email protected]> wrote: > You'd get some sort of set of options for what to do if the repository > version has changed since your version, including @shadow . > > Seemed clever for a moment anyway . . . ah well. Just instead of > comparing between Leonard and Linda by email, just do whatever they > would do as an interaction with the repository. Maybe if the diff is > very great, the version control system would have a contact info > element and you can contact the other person dabbling with the file in > that case. > > I don't know > > > Seth > > On Wed, Dec 11, 2013 at 7:37 PM, Seth Johnson <[email protected]> > wrote: >> (I'm not really back, but a good thought (I think) occurred to me >> reading this one thread. inline . . .) >> >> On Wed, Dec 11, 2013 at 2:04 PM, Edward K. Ream <[email protected]> wrote: >>> On Wed, Dec 11, 2013 at 11:12 AM, Reinhard Engel >>> <[email protected]> wrote: >>> >>>> >>>> 1. Leonard and Linda exchanging data and structures via (Leo generated!) >>>> files. Both are Leo users. So you can rely on the tools Leo offers; and >>>> it's >>>> reasonable to assume that one can consolidate both their file versions. >>> >>> >>> Not so easily. Sure, they could email @file results to each other, but we >>> want something that works with the common work flow. That is, bzr/git, etc. >> >> How about: >> >> @bzr or @git instead of @file? >> >> Or @repository with params for different ones? >> >> What if Leo logged commits in and out of the version control >> repository for you? It might prompt you when it was about to do so, >> so you would be able to choose how often that happens. Or it might >> apply some sort of "good behavior" principle? >> >> </End of thought> >> >> Seth >> >> >>>> 2. Nancy comes into play. >>>> .. >>>> I want to throw an arbitrary file at my @shadow (or whatever better >>>> solution will be developed), and it shall be able to reconstruct the >>>> original structure, even if the structure in the file is upside, all the >>>> names have been changed, the file has grown or shrunk by a factor of two >>>> (whatever), or even it doesn't have (or had) any discernible at all. Is >>>> this >>>> doable? >>> >>> >>> No. It's not possible. That's why @shadow really won't work. >>> >>> Edward >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "leo-editor" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/leo-editor. >>> For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
