It's not nearly that cool yet. I must have updated the version without
updating the docs a while back. While updating the docs I noticed that
there's yet a newer version out.
Isn't there already a script somewhere that pings the download page of
picolisp.com for a newer version? I'd like to stay
Thanks again, David!
When I run this and do “(version)”, I get 16.5.30, while your docs says “This
is version 16.2”. I guess one gets the current stable release version when one
does the “docker pull”. Is that right?
/Jon
> On 22. Aug, 2016, at 02:00, David Bloom wrote:
>
> Docs updated. So
Docs updated. Sorry it took me so long. I'll be quicker to respond in the
future. Added a --rm to automatically remove the container upon exit.
That way you don't have to manually remove any cruft left over in docker ps
-a. Optionally you can decide not to use the --rm switch and be able to
ins
Thanks a lot, David!
/Jon
> On 15. Aug, 2016, at 13:57, David Bloom wrote:
>
> Pardon the delay Jon, I've been under extreme amounts of stress but not
> for much longer. I'll update the docs to reflect getting a Tinycore prompt
> rather than just a REPL.
>
> On Aug 15, 2016 6:08 AM, "Jon Kle
Pardon the delay Jon, I've been under extreme amounts of stress but not
for much longer. I'll update the docs to reflect getting a Tinycore prompt
rather than just a REPL.
On Aug 15, 2016 6:08 AM, "Jon Kleiser" wrote:
> I just want to report that my use of “docker run -v” was not correct. This
I just want to report that my use of “docker run -v” was not correct. This
works much better:
docker run -v /Users/jkleiser/script:/opt/script -it
progit/docker-tinycore-picolisp
I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh"
(echo)) from inside PicoLisp.
/Jon
> On
Hi David,
I have now tried your container as described at
https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got PicoLisp
version 16.5.30 running. Does your container allow me to get access to the
Tinycore Linux command line?
I need to load a PicoLisp file I have on my Mac. I hav
Hi Alex,
There are several reasons why I've created PicoLisp in a container.
1) The image has recently been trimmed down to 14MB. The large image was
just to get something out there and refine it shortly afterwards.
2) I didn't know that there was an existing extension. Is it the latest
version
Why download a 187MB file to "try" PicoLisp in Tinycore when you can just
type: "tce-load -il picolisp" to download/install the 88KB extension ?
I'm sorry, I don't understand the purpose of this.
Alex
On Wed, Jun 1, 2016 at 2:46 PM, David Bloom wrote:
> Thanks to your collective help I'm plea
"One small step for picolisp, a giant leap for computingkind" -- viKid
On Jun 1, 2016 at 4:46 AM, David Bloom wrote:
Thanks to your collective help I'm pleased to announce the availability of
PicoLisp in a docker container! Now anyone with docker installed can try
out 64-bit PicoLisp v16.2 r
That was my plan when I get home from work tonight.
On Jun 1, 2016 12:14 PM, "Mike" wrote:
> create announce on reddit.com/r/lisp
>
> On 1 июня 2016 г., at 17:46, David Bloom wrote:
>
> Thanks to your collective help I'm pleased to announce the availability of
> PicoLisp in a docker container!
create announce on reddit.com/r/lisp
> On 1 июня 2016 г., at 17:46, David Bloom wrote:
>
> Thanks to your collective help I'm pleased to announce the availability of
> PicoLisp in a docker container! Now anyone with docker installed can try out
> 64-bit PicoLisp v16.2 running on Tinycore Linu
12 matches
Mail list logo