--
SuperSaiyanBlue
What does setf do that set or setq can't do?
On June 27, 2019 4:51:13 AM UTC, Bruno Franco
wrote:
>Soo, yeah. I'm studying common lisp, and coming from picolisp setf
>confused
>me at first. The concept does not seem to appear on picolisp, and I
>wondered why its not there.
>
>The only reference
You can try adding the `its-pointless` repo. It provides a few extras not found
in the main repo example julia, gcc-6/7/8, gforth, picolisp too (just got
updated from v18 to v19)
Just follow the instructions given in the readme file here
https://github.com/its-pointless/gcc_termux
On July
Being the biggest privacy violator I'm not sure I could ever be there.
(https://stallman.org/facebook.html)
There's an inactive picolisp subreddit which could be resurrected and isn't as
bad. Perhaps, that would be better. https://old.reddit.com/r/picolisp/
On November 20, 2019 6:22:52 AM
>That's nice indeed!
>
>Perhaps we should also place a link to the post in picolisp.com?
Done. Added a link to all posts tagged picolisp under documentation/Other
resources site section.
https://adamo.wordpress.com/tag/picolisp/
--
SuperSaiyan Blue
--
UNSUBSCRIBE:
Hi list!
I have some .htm and .txt files and wish to serve them via the picolisp
webserver. Unfortunately, the mime function doesn't work the way I want it to
work.
The files aren't getting sent as 'text/html' or 'text/plain' for htm and txt
respectively.
Curl says the files are sent as
>Correct. @lib/http.l has in '*Mime':
> (`(chop "txt") "text/octet-stream" 1 T)
>".htm" is not in '*Mime'. You can add an entry with 'mime' upon startup
>of your
>program:
> (mime "htm" "text/html; charset=utf-8")
I did try that but it did not work. The reason i asked :-)
Files:
>It must be passed to the main server process.
>
>I tried this:
>
>$ pil @lib/http.l @lib/xhtml.l -'mime "txt" "foo/bar; mumble"' --server
>9091 tst.l
Wow, you are right!
This is the improvised code which solves both:
$ pil @lib/http.l @lib/xhtml.l -'(and(mime "txt" "text/plain;
>This is not correct. -'(and (mime ...))' results in ((and (...))) and
>will most
>probably crash (executes the *return* value of 'and' as a function).
Right! Luckily it didn't crash here.
>The 'and' is not needed anyway. I would recommend
>...
>or, better, create a file which initializes it
