On Fri, 8 Jun 2018 09:16:58 -0700 (PDT)
"Edward K. Ream" wrote:
> Investigate whether the --no-cache command-line option is still
> needed. This is a non-trivial question, because Leo caches things
> like the current position, etc. It may be that only the "global" db
> key will be used, but we
In a day or two I expect to merge the fast-read branch into devel. That
will be an important milestone.
We can then turn our collective attention to extending what Leo can do.
I'd like to start a "virtual sprint" here, but that must wait until all
speed-related work is completely finished.
On Thursday, June 7, 2018 at 11:14:52 AM UTC-5, Edward K. Ream wrote:
>
> I have been eating my own dog food all morning, with no signs of trouble.
>
Recent revs have completed the fast-read branch. We are close to being able
to merge the fast-read branch into devel. The almost-never-used
This merge should be completely safe because the FAST switches in
leoAtFile.py and leoFileCommands.py are False. As a result, all of the
great new code in the "fast-read" branch is disabled.
All the great new code in the "perf" branch *is* functional. The only
difference you should see will
