Search
Thursday, 21st of February 2019, 3:44:32 UTC
8:28:58
Colleen
http://shinmera.tymoon.eu/public/scream.wav
9:02:45
no-defun-allowed
whoa that's not a healthy scream
9:03:01
Colleen
http://shinmera.tymoon.eu/public/scream2.wav
9:07:50
theemacsshibe
https://youtu.be/LQiOA7euaYA?t=224
9:07:51
Colleen
www.youtube.com/watch?v=LQi... Website (HTML), Title: Talking Heads - Road to Nowhere (Official Video) - YouTube
9:08:19
theemacsshibe
hi, no-defun-allowed here, interweb connection is being flaky again
9:17:22
phoe
Shinmera: somebody intelligent at work decided to fix a bug on my Windows VM by wrecking it altogether. I no longer have a Windows VM with a usable Lisp toolchain.
9:17:42
phoe
They literally killed the whole Windows profile I had.
9:20:02
Shinmera
and naturally there's no backups
9:21:27
phoe
If they don't have a backup of my profile, I'll squeeze one out of them nonetheless
10:26:47
phoe
Shinmera: please treat me as a Windowsless person for the time being
10:31:25
phoe
not only I'll need to rebuild my Windows
10:31:43
phoe
but I'll also need to wait a while to even think of starting the rebuild
12:36:46
phoe
I just realized that the exports for drag and drop and draggable are inconsistent with documentation
13:13:52
phoe
I got lost in the exported symbols again
13:16:57
phoe
for basic stuff, make sure that there is an exact match between each symbol exported from #<PACKAGE QUI> and docs in documentation.lisp and that each docstring's type matches the way in which that symbol is bound
13:17:15
phoe
so if you have docs like (type foo "...") then ensure that FOO is exported and it is typebound
13:17:26
phoe
and that there are no stray symbols anywhere
13:17:38
Shinmera
Colleen: tell phoe look up documentation-utils check
13:17:38
Colleen
phoe: Function documentation-utils:check https://shinmera.github.io/documentation-utils#FUNCTION%20DOCUMENTATION-UTILS%3ACHECK
13:18:25
phoe
does it take only exported symbols into account?
13:18:32
phoe
because I don't think we want docstrings for stuff like %PANEL-OVERRIDE-MOVE-EVENT.
13:18:43
Shinmera
did you look at the function signature my boy
13:20:24
Shinmera
not slept well recently?
13:24:23
phoe
not at all - stress, smog, nightmares and a funeral
13:24:52
phoe
well I still don't have cancer
13:25:06
Shinmera
everyone's got a bit of cancer
13:26:55
phoe
ok, you're right then, I got the full package
13:28:43
phoe
https://github.com/Shinmera/documentation-utils/blob/8215cb1c14b0007fb53829e8804a1b213555cf82/toolkit.lisp#L62
13:28:44
Colleen
github.com/Shinmera/documen... Website (HTML), Title: documentation-utils/toolkit.lisp at 8215cb1c14b0007fb53829e8804a1b213555cf82 · Shinmera/documentation
13:31:22
phoe
also (define-documentation-test type (symb) (find-class symb NIL)) won't work for types that ain't classes
13:31:55
Shinmera
Yeah, but there's no way to get that info anyway so
13:32:15
Shinmera
there is no standard way to test whether a symbol is deftyped or not
13:32:30
phoe
#'swank/backend:type-specifier-p
13:32:39
phoe
and since you don't want to depend on swank
13:33:01
phoe
you can just copy all the implementations of that function and stuff it into some sorta github.com/Shinmera/type-utils
13:33:08
Shinmera
that's not a standard way, that's a semi-portable way :)
13:33:24
Shinmera
Colleen: tell phoe look up definitions
13:33:24
Colleen
phoe: About definitions https://shinmera.github.io/definitions#about_definitions
13:34:10
phoe
Shinmera: well, that's right
13:34:29
Shinmera
definitions could do with more backends, but I'm laaaazy
13:34:51
phoe
definitions depends on documentation-utils
13:34:57
phoe
so documentation-utils cannot depend on definitions
13:35:51
phoe
also do you have a library for freaking everything I can think of
13:35:59
Shinmera
Anyway, docutils should not depend on anything to begin with
13:36:14
Shinmera
unfortunately I do not
13:36:44
Shinmera
there's still so much to yak-shave
13:37:58
phoe
(ql:quickload :yak-shaver)
13:39:22
Shinmera
by the way if you have other projects to add xref to colleen for, lemme know
13:40:14
Shinmera
It has a lot of the standard libraries already. https://github.com/Shirakumo/maiden/blob/master/agents/lookup/archives.lisp
13:40:15
Colleen
github.com/Shirakumo/maiden... Website (HTML), Title: maiden/archives.lisp at master · Shirakumo/maiden · GitHub
13:56:09
hjudt
Shinmera: i know js is not your favorite, but i am having trouble using js fetch api (https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch) for posting data to the radiance API. the data doesn't seem to get through. curl and dex:post work though. any idea what could be wrong (i'll post an example)?
13:56:10
Colleen
developer.mozilla.org/en-US... Website (HTML), Title: Using Fetch - Web APIs | MDN
13:56:58
hjudt
fetch('/my-server-api-url/', { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ env: "test"}) })
13:57:32
hjudt
is there any way i can debug this? i mean, check what is received by radiance?
13:58:04
hjudt
that is, perhaps the raw request before it is parsed?
13:59:44
Shinmera
that'll depend on what server backend you're using
13:59:46
hjudt
when i inspect radiance:*request*, data and post-data hash-tables are both empty.
13:59:53
hjudt
server backend is hunchentoot
14:00:24
Shinmera
I don't recollect if hunchentoot has a debug setting to print what it's getting
14:00:42
hjudt
i have the same problem with the axios js lib (that's why i tried fetch), but not with jquery's $.post
14:01:15
Shinmera
Well, Radiance does almost nothing, really. It just takes the data it gets from hunchentoot/whatever and stuffs it in the request object
14:01:28
hjudt
ok, so i need to look into hunchentoot then
Thursday, 21st of February 2019, 15:44:32 UTC