Re: The fast-colorizing branch: a revolution in syntax coloring

2017-01-16 Thread Edward K. Ream
On Sun, Jan 15, 2017 at 11:44 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > > Once in a while I am seeing this, with both Python 3 and 2: > > > > Internal Leo error in bodyString > > not unicode: (the actual string) > > Called from

Re: The fast-colorizing branch: a revolution in syntax coloring

2017-01-15 Thread 'Terry Brown' via leo-editor
On Sun, 15 Jan 2017 04:44:11 -0800 (PST) "Edward K. Ream" wrote: > On Sunday, January 15, 2017 at 6:53:32 AM UTC-5, Edward K. Ream wrote: > > *I have not tested this code with Python 2*. > > > > It turns out that colorizer.colorize *is* called, but only with > python 2.

Re: The fast-colorizing branch: a revolution in syntax coloring

2017-01-15 Thread Edward K. Ream
On Sunday, January 15, 2017 at 6:53:32 AM UTC-5, Edward K. Ream wrote: *I have not tested this code with Python 2*. > It turns out that colorizer.colorize *is* called, but only with python 2. Once in a while I am seeing this, with both Python 3 and 2: Internal Leo error in bodyString not

Re: The fast-colorizing branch: a revolution in syntax coloring

2017-01-15 Thread Edward K. Ream
On Sunday, January 15, 2017 at 6:43:44 AM UTC-5, Edward K. Ream wrote: > > > 3. From an engineering standpoint, it revolutionizes Leo's approach to > Qt's QSyntaxHighlighter class. In essence, *everything happens > automatically*. > *I have not tested this code with Python 2*. This must be

The fast-colorizing branch: a revolution in syntax coloring

2017-01-15 Thread Edward K. Ream
The fast-colorizing git branch is a revolution in syntax coloring, while using the bulk of Leo's existing coloring code. The new code supports all of the languages in leo/modes. Please test this branch for at least a day or so before being merged into the main line. Please report any problems