Search
Thursday, 4th of June 2020, 21:35:59 UTC
21:36:43
jcowan
sorry, make that T and NIL
21:37:02
Shinmera
There's also no hashref
21:37:35
jmercouris
(ql::http-fetch "http://beta.quicklisp.org/quicklisp.lisp" #P"/Users/jmercouris/Downloads/quicklisp-JBCUCRBI.lisp")
21:37:37
Shinmera
As for 'how', you'll have to go through the symbol index.
21:37:39
jmercouris
Does not make a file, why not?
21:38:05
jmercouris
can anyone confirm if ql:http-fetch is working on their machines as I expect it to be for myself?
21:38:45
jmercouris
I also tried the variation: (ql-http:http-fetch "http://beta.quicklisp.org/quicklisp.lisp" #P"/Users/jmercouris/Downloads/quicklisp-JBCUCRBI.lisp")
21:39:07
jcowan
Anyway, what else uses that result protocol?
21:39:12
_death
function-lambda-expression returns 3 values, that you can think of as generalized booleans.. same goes for get-properties
21:40:23
Shinmera
Not sure about standard functions, but a bunch of libraries make use of that convention.
21:43:19
jmercouris
hm, that's frustrating
21:43:26
jmercouris
it must be OS specific or configuration specific
21:43:28
Shinmera
jmercouris: if it didn't work, the quicklisp-installer wouldn't work either.
21:43:43
jmercouris
Yes, that's what I deduced
21:43:51
_death
jmercouris: you could try wireshark.. or adding print statements..
21:44:14
jmercouris
adding print statements? where is http-fetch even defined?
21:44:36
_death
don't think you can trace CL operators
21:44:38
jmercouris
I don't even know to which system the ql-http package belongs
21:45:18
jmercouris
it puts me to a strange file
21:45:28
jmercouris
it takes me to here: /Users/jmercouris/Source/Lisp/qlot/proxy.lisp
21:45:44
Shinmera
_death: it's not required to work but you can do it
21:46:14
jmercouris
I don't understand all of this indrection in proxy.lisp
21:46:29
jmercouris
I'm sure there is some reasoning, what it is, I can't know
21:46:32
_death
jmercouris: does it redefine ql-http:http-fetch?
21:46:40
jmercouris
(setf (fdefinition (find-symbol (string '#:http-fetch) '#:ql-http))
21:47:16
jmercouris
I mean it kind of makes sense I guess, maybe
21:47:22
jmercouris
probably a lot of hacks to get Qlot to work
21:47:42
jmercouris
https://github.com/fukamachi/qlot/blob/master/proxy.lisp
21:48:56
_death
well, now can see which one is to blame.. (I've a good guess)
21:48:56
jmercouris
_death: to clarify, did ql-http:http-fetch work for you?
21:49:05
_death
yes.. but I don't have qlot
21:49:15
jmercouris
yes, let me try in a fresh image without qlot quickloaded
21:49:30
jmercouris
this time, it worked
21:49:38
seoushi
http-fetch works for me. Had to be in the ql package tho since http-fetch is not external
21:49:54
jmercouris
you must have ql::http-fetch or ql-http:http-fetch
21:50:15
jmercouris
_death: what is your guess?
21:51:02
jmercouris
also what is qlot://localhost/???
21:51:18
jmercouris
qlot is a protocol now?
21:52:16
jmercouris
hm I changed it to #-quicklisp, and it worked
21:52:44
jmercouris
can you enlighten me what this is trying to do? add proxy support to quicklisp?
21:55:47
_death
if the url begins with the qlot prefix, it makes sure *proxy-url* is nil
21:56:14
jmercouris
what does that achieve?
21:56:26
jmercouris
the branch I can understand no problem
21:56:35
jmercouris
I'm wondering about a bigger picture explanation
21:56:41
jmercouris
why would this ever be necessary???
21:56:58
jmercouris
anyways, thanks for the debugging help
21:57:19
_death
I don't know much about qlot
22:05:40
_death
Shinmera: interesting that it works (for OPEN).. thanks
23:08:33
Lord_of_Life_
** NICK Lord_of_Life
3:10:08
beach
Good morning everyone!
4:10:49
emacsomancer
morning, beach!
6:33:26
phoe
beach: regarding the shortness of the condition system, the original isn't very long either - see http://www.nhplace.com/kent/CL/Revision-18.lisp
6:36:21
phoe
the largest bloaters, size-wise, are all the DEFINE-CONDITIONs. And the largest bloater, cognition-wise, IMO, is HANDLER-CASE with its :no-error case
6:38:18
phoe
as Stas once said, a condition system is easy; dynamic variables, UNWIND-PROTECT, and GO/RETURN-FROM are hard
6:42:37
beach
phoe: I see, yes. We have already taken care of the hard parts in SICL then.
6:49:01
beach
phoe: Would you like to work on SICL with us?
6:50:06
phoe
beach: I will possibly be able to contribute a thing or two, sure. My main focus will be CLUS as soon as my book is finished, but I think I'll be able to add this or that to SICL in meantime.
6:50:38
beach
Sounds great! Do you have a preferable subject you would like to dig into?
6:50:50
phoe
the condition system, unsurprisingly
8:45:04
heisig
I was just made aware that PLDI 2020 is hosted online and participating is for free: https://conf.researchr.org/home/pldi-2020
8:45:11
heisig
The registration deadline is today.
8:45:54
heisig
(I know this is not strictly on topic, but it might interest plenty of people nevertheless)
8:57:04
easye
heisig: Thanks for the info on PLDI. Interesting to me...
9:09:02
beach
heisig: That's good news.
9:22:59
White__Flame
** NICK White_Flame
Friday, 5th of June 2020, 9:35:59 UTC