The master branch now suffers *three* serious problems. I recommend you immediately do git checkout 570f296e7 to restore things to a safer state of affairs. Fixing the master branch may take an hour or more.
If you have pulled the master recently, *please read the following carefully*, especially point 1 below. My sincere apologies for this mess. 1. The most serious problem is with Leo's write logic. Leo *will change external files unnecessarily* in some circumstances. An incredible blunder at ea3273a84 causes Leo to write *all* lines starting with '@' as if they were Leo directives. This isn't fatal: Leo reads such lines correctly. Small consolation: the changes are completely unnecessary. 2. Rev 4b5b744 broke syntax coloring for python strings. Starting the strings colors until the next string delimiter, as usual, but *completing* the string doesn't undo the coloring for the following lines. This is a great clue for me, but it is unbearable in practice. 3. The recent "improvement" to Leo's scripting code can break @button nodes that don't explicitly start with @language python. This only happens if the .leo file's default target language is rest or markdown/md. I'll fix all these asap. Again, my sincere apologies. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
