Maybe it has something to do with apt-get upgrade as well?
Glad to hear the issue disappeared!
2018-04-18 14:16 GMT+02:00 Joe Bogner :
> Arie, I followed your WSL steps on a newer machine and I don't see the db
> locking issue any more. Thanks! My other machine has the problem but its
> WSL is at
Hi Arie,
> @Joe could you show me an example where db locking didn't work?
> Maybe I can test this and see if it does work correctly in the way I
> now set up PicoLisp in WSL?
You don't even need a DB to test the locking, the 'ctl' function will do.
To test it, open two terminals and start
Arie, I followed your WSL steps on a newer machine and I don't see the db
locking issue any more. Thanks! My other machine has the problem but its
WSL is at least 6 months old - so maybe it was fixed in WSL since then or
possibly something fixed/changed by following your instructions. Thanks,
I'll
Hi Alex,
1) root mode was because I tried a lot of different things, but missed the
obvious family64.tgz 😡
2) had a few problems with cd-ing into folders, because under Windows it is
a bit different
So, after unpacking family64.tgz into a local folder in my home dir
everything works great!
Now s
Hi Arie,
> * root@HP-Arie:/usr/share/doc/picolisp/doc# **pil family.l -main -go +*
> ...
> *!? (pool "family/" *Dbs) "family/" -- Open error: No such file or
> directory ?*
This is probably because the "family/" directory does not exist yet. Or did you
unpack the file "family64.tgz"?
In ge
Hi,
tried this:
*​ root@HP-Arie:/usr/share/doc/picolisp/doc# *​
*pil @lib/http.l --server 8080 @doc/hello.l -wait*
works OK! Can use the GUI from within standard Windows in browser.
But this:
* root@HP-Arie:/usr/share/doc/picolisp/doc# **pil family.l -main -go +*
fails with:
*!? (pool "fami