Re: New backend for Leo Cacher

2017-07-31 Thread vitalije
> > ​Did you push master? I don't see SQLITE=True in leoCache.py​. And yes, > it's working for me. > > Edward > Done at a1043408d. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails

Re: New backend for Leo Cacher

2017-07-31 Thread Edward K. Ream
On Mon, Jul 31, 2017 at 3:51 AM, vitalije wrote: > I think I've been using this pretty consistently without any issues on >> three installs - I only notice when I `git pull` and have to re-edit >> leoCache.py. So wondering if we should switch to True for everyone for >>

Re: New backend for Leo Cacher

2017-07-31 Thread vitalije
> > I think I've been using this pretty consistently without any issues on > three installs - I only notice when I `git pull` and have to re-edit > leoCache.py. So wondering if we should switch to True for everyone for > wider testing? > > I am also using this and few problems that I have

Re: New backend for Leo Cacher

2017-07-30 Thread Terry Brown
On Tue, 18 Jul 2017 14:35:19 -0500 "Edward K. Ream" wrote: > On Tue, Jul 18, 2017 at 2:22 PM, Terry Brown > wrote: > > > On Mon, 17 Jul 2017 11:05:51 -0700 (PDT) > > vitalije wrote: > > > > > Fixed at 8d6a7ab. My fault, sorry

Re: New backend for Leo Cacher

2017-07-18 Thread Edward K. Ream
On Tue, Jul 18, 2017 at 2:22 PM, Terry Brown wrote: > On Mon, 17 Jul 2017 11:05:51 -0700 (PDT) > vitalije wrote: > > > Fixed at 8d6a7ab. My fault, sorry about that. Recently, I have > > switched to Python3, and now I am making Python2 crashers. > >

Re: New backend for Leo Cacher

2017-07-18 Thread Terry Brown
On Mon, 17 Jul 2017 11:05:51 -0700 (PDT) vitalije wrote: > Fixed at 8d6a7ab. My fault, sorry about that. Recently, I have > switched to Python3, and now I am making Python2 crashers. I've switched SQLITE = True in three Leo installs and not seen any problems since 8d6a7ab.

Re: New backend for Leo Cacher

2017-07-17 Thread vitalije
Fixed at 8d6a7ab. My fault, sorry about that. Recently, I have switched to Python3, and now I am making Python2 crashers. Vitalije -- 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

Re: New backend for Leo Cacher

2017-07-17 Thread Terry Brown
I got setting leoID from os.getenv('USER'): 'tbrown' reading settings in /mnt/usr1/usr1_t/Package/leo/git/leo-editor/leo/config/leoSettings.leo reading settings in /home/tbrown/.leo/myLeoSettings.leo Leo 5.5, build 20170715081418, Sat Jul 15 08:14:18 CDT 2017 Git repo info: branch = master,

Re: New backend for Leo Cacher

2017-07-17 Thread Edward K. Ream
On Sun, Jul 16, 2017 at 3:28 PM, vitalije wrote: Commit 0e98b2073 contains new backend for leoCache.Cacher. New code is > disabled by default by `SQLITE=False` switch in leo/core/leoCache.py > ​Thanks for this. I'll look at it asap. Edward -- You received this message

New backend for Leo Cacher

2017-07-16 Thread vitalije
Commit 0e98b2073 contains new backend for leoCache.Cacher. New code is disabled by default by `SQLITE=False` switch in leo/core/leoCache.py To try it set `SQLITE=True`. On next launch Leo will have to read and parse all external files, like it does after cleaning cache. But following launches