On Fri, Jan 13, 2017 at 5:25 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote:
> Congrats on finding the culprit. Thank you. Strangely, the performance bug *remain*s (sometimes) in the legacy coloring code. I allude to this in this morning's announcement <https://groups.google.com/forum/#%21topic/leo-editor/-bA7kCcQnVE>. The bug now seems even more mysterious. Calling QTextDocument.markContentsDirty does not cause a recoloring. As before, calling rehighlight directly is super slow. Note: if a huge node is selected when Leo starts, that node is colored quickly(!). But revisiting the node later is slow. I have spent several hours on this new mystery. The best clue is that the body pane's QTextDocument keeps changing with the legacy code, but remains invariant (as expected) when using pyzo. Presumably, finding out why the document changes will allow the bug to be fixed. > Couple of things I'd like to see in Leo syntax highlighting, highlighting of trailing whitespace, and highlighting of https://en.wikipedia.org/ wiki/Non-breaking_space and also of tab (\t). The show/toggle-invisibles commands will do some of this. Please file a bug report if non-breaking spaces aren't shown to your satisfaction. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
