I am also often delighted by the little things Alex has added to PicoLisp
to make life easier. It's full of little gems like 'pil' which make it such
a wonderful language to use.
On Sun, Aug 23, 2015 at 7:41 PM, Erik Gustafson
wrote:
>
> Hi Alex,
>
> first of all, thanks Erik for the nice "Unnes
Hi Alex,
first of all, thanks Erik for the nice "Unnest" article!
>
Of course!
> In fact, there is a function 'pil' for that. It can be used to access
> files in ".pil/" in the user's home directory.
>
Must you always come up with the most convenient and elegant solutions to
these sorts of thi
Beneroth,
You usually start the picolisp repl by executing 'pil', watch it in a text
> editor and you can see it is actually a simple script using the #!
> mechanism to start the 'picolisp' binary, followed by loading a few files
> from @lib/.
>
Thanks for the tip, I had never looked inside befor
Hi Erik + Andreas,
first of all, thanks Erik for the nice "Unnest" article!
> > what's the canonical way to customize the default 'pil' environment?
> > I'd like to have some of my own utilities and other goodies loaded when I
> > start up.
> > Can I just stick the necessary calls to (load) in
> what's the canonical way to customize the default 'pil' environment?
> I'd like to have some of my own utilities and other goodies loaded when I
> start up.
> Can I just stick the necessary calls to (load) in .pilrc? :)
I'm not aware of any .pilrc mechanics, search in mailing list also yields
