On Jan 19, 9:14 am, "Edward K. Ream" <[email protected]> wrote: > On Tue, Jan 19, 2010 at 3:34 AM, James Wilson <[email protected]> wrote: > > My first Leo related Aha: this language-by-language syntax > > highlighter, when combined with restructured text, will allow Leo to > > do virtually everything that anyone who wants Leo to support rich text > > Interesting. Especially if it works :-)
Rev 2706 fixes a significant colorizer bug that caused your problem. Previously, the colorizer inited the so-called configuration tags only once, which is wrong. These tags are what the @font settings specify. Now, the colorizer inits the tags when the language changes when switching nodes. Usually the language doesn't change, so the new code will be approximately as fast as the old. test.leo presently contains an enabled example of using @font nodes for keyword 2 and 4 tags for @language rest. The effect is pretty cool, but not perfect, because the '*' characters are still visible. Edward
-- 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.
