On Fri, Feb 27, 2009 at 7:39 PM, Edward K. Ream <[email protected]> wrote:
> Each node would be preceded by a single hint: > > #...@node:<gnx>: <headline> > > That's *all*. In particular, **indentation of the hint determines outline > structure.** Aren't you descringing a cleanup of @thin node sentinels here, instead of adding sentinels to @auto nodes? And I agree w/ Terry here: QQQ 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. QQQ As long as @shadow is completely safe, it probably should be used instead of @auto nodes. The problem with both @shadow and @auto is that rearranging nodes can result in different order in the final file (which annoys collaborators). Perhaps the default save functions should just warn about this and abort, requiring the user to explicitly run save-at-shadow-nodes to really flush the changes to disk? Command to restore the "correct" node order (w/ the cost of destroying outline structure) should be provided as well. This may seem like safety exaggeration, but it's essential that leo is deemed "safe", so partial buy-in is possible. I have an issue with rearrangement of @thin nodes as well. Sometimes, when you look at bzr history of leo, you will note *huge* diffs, as if half of the file changed. This should be minimized to make things like "bzr annotate" count. Also one of the reasons I don't like things like sort-siblings to be so easy to execute ;-) -- Ville M. Vainio http://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 -~----------~----~----~----~------~----~------~--~---
