Re: Searching on LeoEditor site is broken

No. As Chris George mentioned, searching from within the documentation does not work. Rob... On Monday, December 18, 2017 at 7:07:25 AM UTC-5, Edward K. Ream wrote: > > > > On Fri, Dec 8, 2017 at 7:47 AM, Largo84 > wrote: > >> Try doing a search for any topic on Leo's main

Re: Searching on LeoEditor site is broken

The Google search on the home page works as expected. The "Quick Search" on the table of contents works as largo84 notes above. Chris On Mon, Dec 18, 2017 at 4:07 AM, Edward K. Ream wrote: > > > On Fri, Dec 8, 2017 at 7:47 AM, Largo84 wrote: > >> Try

Re: Missing settings nodes for body pane focus colors?

On Fri, Dec 15, 2017 at 6:21 PM, tscv11 wrote: > I'm sure they've just moved or morphed into something better, but I can't > find either of the settings below in leoSettings.leo. They were mentioned > in a discussion here so I was surprised they weren't present. > > @bool

Re: The cft crash: understanding vs type checking

On Fri, Dec 8, 2017 at 8:47 AM, Terry Brown wrote: > On Fri, 8 Dec 2017 04:37:01 -0800 (PST) > "Edward K. Ream" wrote: > > > 3. The nodetags.py plugins caches vnodes. This is fine as long the > > plugin (in effect) recreates the cache when the

Re: Why I believe that using class based prototyping is suboptimal

On Monday, December 18, 2017 at 7:57:34 AM UTC-6, Edward K. Ream wrote: Heh. This is likely a colorizer performance bug, arising from the large number of section references in the top-level node. I have just opened #639: Colorizer is very slow when a node has thousands of section references

A new tag pattern: # tag:

This is a lightweight, Leonine tag pattern. Just create a comment like # tag:setter. I used this when studying the check-conventions code. I did a regex pattern on ']\s*=' and then added the comment lines just before the assignments. To create the nodes, I can just do cff: tag:setter. It's

Re: Why I believe that using class based prototyping is suboptimal

On Monday, December 18, 2017 at 7:46:09 AM UTC-6, Mike Hodson wrote: Thanks. I've got the files now. 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

Re: Why I believe that using class based prototyping is suboptimal

On Mon, Dec 18, 2017 at 6:22 AM, vitalije wrote: > > > > Just tested the link, about 150k for me ?! > ​Still zero for me. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Why I believe that using class based prototyping is suboptimal

On Monday, December 18, 2017 at 12:51:11 PM UTC+1, Edward K. Ream wrote: > > On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: >> >> >> JavaScript files are here >> > > The .zip files has zero bytes. > > Edward > Just tested the link,

Re: Requirements for Curses console mode

On Sat, Dec 16, 2017 at 2:55 PM, Matt Wilkie wrote: > Found it! The missing dependency is python-tk, which I needed to install > with apt. > > I discovered it by loading LeoPlugins.leo in graphical Leo, navigating to > @file > cursesGui2.py and using Ctrl-B, where I then

Re: Searching on LeoEditor site is broken

On Fri, Dec 8, 2017 at 7:47 AM, Largo84 wrote: > Try doing a search for any topic on Leo's main web site and you will > likely get something like this (searched for 'mark'): > ​It looks like this is working now. Is it working for you? Edward -- You received this message

Re: Why I believe that using class based prototyping is suboptimal

On Mon, Dec 18, 2017 at 5:51 AM, Edward K. Ream wrote: > On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: >> >> >> JavaScript files are here >> > > The .zip files has zero bytes. > ​Leo's js importer might choke

Re: Why I believe that using class based prototyping is suboptimal

On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: > > > JavaScript files are here > The .zip files has zero bytes. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Why I believe that using class based prototyping is suboptimal

Do these problems still exist? If so, please send me the file. > Here is test code: import timeit fileName = '/tmp/rpg_objects.js' p1 = p.insertAfter() p1.h = '@auto ' + fileName def doit(): c.importCommands.createOutline(fileName, parent=p1.copy()) t = timeit.timeit(doit, number=1)

Re: Why I believe that using class based prototyping is suboptimal

On Saturday, December 16, 2017 at 4:05:58 PM UTC-6, vitalije wrote: > In April 2017, Edward wrote about [importer problems] on this forum and I decided to look into it. > When I tried to import one javascript file, on my greatest surprise, Leo was blocked more than a minute. That's

Wrapping up check-conventions for awhile

It's time to summarize the state of the check-conventions (aka cc) command before traveling. *tl;dr:* Read the summary *Status* 1. Most importantly, this project does real checking, something that none of my type-related projects has ever done before. The cc.resolve* methods are simple and

Travelling soon for about a month

I'll be traveling with Rebecca for 4-5 weeks starting Wednesday. I'll answer emails before than, something that I've been neglecting while working on the check-conventions command. I'll summarize the present state of check-conventions in another thread. Edward -- You received this message