On Thu, 17 Aug 2017 10:18:31 -0500
Kent Tenney wrote:
> Is current master considered safe?
p.s. I think all those warnings have expired. I haven't seen any
issues with light use of yesterday's master.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" g
On Thu, 17 Aug 2017 10:18:31 -0500
Kent Tenney wrote:
> How does one use the new db backend?
> is it config, command line option, default ... ?
I think sqlite db based caching is on by default in master. As far as
I know the new tech. is currently confined to caching, using .db format
for outli
How does one use the new db backend?
is it config, command line option, default ... ?
I haven't pulled for a while, there were some warnings
Is current master considered safe?
Thanks,
Kent
On Thu, Aug 17, 2017 at 9:54 AM, Edward K. Ream wrote:
> Representing .leo files as .db files is an impor
Representing .leo files as .db files is an important new capability. It's
going to stay, because using .db files is completely optional.
However, I am not clear what their advantage is. On my (fast) machine, the
difference in load times is negligible:
- Loading 3 .db files and 1 .leo file: 7.6
Since plugins are so simple in leo, yes I made them so. Since I have your
endorsement I'll begin applying leo and python codons standards to it and
give what I have, plus suggestions for enhancement and issues over the
weekend or next week.
On Aug 17, 2017 9:20 AM, "Edward K. Ream" wrote:
>
>
>
On Wed, Aug 16, 2017 at 6:19 PM, Adrian wrote:
> Hello,
>
> I have built a few plugins still a bit rough but workable for PHP:
>
> PHP unit tests (adds @phpunit directive)
> PHP Execute (add @phpexe directive)
> PHP Completer - Uses a prebuilt Sqlite DB with over 14k symbols.. In
> addition it pa
