On Wed, Nov 6, 2013 at 2:11 PM, Viktor Ransmayr <[email protected]>wrote:
> >From a user experience/ workflow POV it feels wrong to me: Yes. Finally I agree with and see the root cause. Recently, I removed all the @file nodes from LeoDocs.leo. I did this because using them was much too clumsy for my taste. But the effect of removing the @file nodes is that *any* change to the documentation will change LeoDocs.leo. In this regard, LeoDocs.leo is like LeoPyRef.leo and LeoPluginsRef.leo, but even worse! You seem to be the only person to have wanted to change LeoDocs.leo. It's a perfectly reasonable thing to do! I don't see a great solution. When you change LeoDocs.leo you have several options: 1. Ignore *your* changes. Do bzr revert. 2. Broadcast your changes by resolving the bzr conflict. There aren't any great tools for doing this, although the file-compare-leo-files command might help a tad. Usually, I "resolve" such conflicts by *replacing* one .leo file by another. But of course that's not great. 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.
