On Sun, Feb 15, 2015 at 2:07 PM, vitalije <[email protected]> wrote:
What if Leo before writing Leo-outline replaces those lines with actual > content they would have in target file > Thanks for this idea. I don't think it is necessary. Leo already has a convention for reading @doc parts when reading @file nodes. This is is kind of an Easter Egg: it allows Leo to reconstruct doc parts exactly (including line breaks) using trailing blanks as markers. See the Post Script for details. It seems to me likely that this code is not being used when reading @nosent files. I'm not sure what is going on, but a fix is likely to be easy. This may eliminate the need for a post-pass that runs just after the update algorithm. I intend to straighten this out today. Edward P.S. Here is the convention. Iirc, it applies to @file nodes as well as the @root nodes that were in use back in the day. It's documented in the history of Leo section of LeoDocs.leo. QQQ We can use the following convention to determine where putDocPart has inserted line breaks: A line in a doc part is followed by an inserted newline if and only if the newline is preceded by whitespace. This is an elegant convention, and is essentially invisible to the user. Tangle outputs words until the line would become too long, and then it inserts a newline. To preserve all whitespace, tangle always includes the whitespace that terminates a word on the same line as the word itself. Therefore, split lines always end in whitespace. To make this convention work, tangle only has to delete the trailing whitespace of all lines that are followed by a 'real' newline. QQQ EKR -- 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/d/optout.
