freenode/#lisp - IRC Chatlog
Search
17:26:05
jmercouris
I've noticed when loading my own code which depends on other libraries, slime compilation will report their warnings, any way to get rid of those?
17:26:26
jmercouris
I'm not interested in stuff like: Unknown location: redefinition: redefining CL-PREVALENCE:GET-ID in DEFGENERIC
17:33:44
Josh_2
Shinmera: when using (complete-authentication <pin>) pin is supposed to be the url returned by initiate-authentication?
17:37:28
Nilby
jmercouris: My advice is always wrong, so you definitely shouldn't do this: https://plaster.tymoon.eu/view/2380#2380
17:49:57
Nilby
(ql:system-apropos "") | wc -l ⇒ 4491 , so that might take a while. My systems have no unintentional warnings
17:57:37
shka_
so you can https://github.com/sirherrbatka/vellum/blob/1315f04382547f938f4569f2b99ba038e93f75b6/run-tests.lisp#L11
18:17:54
Nilby
I still have a CL twitter client with a TUI back from when you had to send your password in cleartext over http, but then I never looked a twitter again.
18:59:38
Josh_2
Shinmera: the fun (statuses/update-with-media ..) says it takes either a pathname, usb-8 array or a base64 encoded string (in the docstring), I have just given it a usb-8 array and I get the error "Wanted one of (FUNCTION FILE-STREAM STREAM PATHNAME)."
20:18:38
contrapunctus
Uh, what's going on here :\ (ql:quickload :mcclim) => System "mcclim" not found 🤔
20:21:10
contrapunctus
phoe: yup, tried that. Although rather suspiciously, it said "1 dist to check"
20:23:12
Shinmera
Josh_2: oAuth tokens don't expire unless they're manually revoked. You have to actually save the info though.
20:23:49
mfiano
First check (ql:where-is-system :alexandria) to see if Quicklisp even has it downloaded
20:25:08
contrapunctus
mfiano: nil 🤔 but I have a /home/anon/quicklisp/dists/quicklisp/archives/alexandria-20200925-git.tgz
20:26:09
Bike
do you have cl-asdf or anything installed? maybe your global asdf configuration is something odd now
20:28:03
phoe
and if for some reason it isn't available, quicklisp has its own fallback asdf that it uses for such situations
20:35:59
contrapunctus
phoe: removed cl-quicklisp, deleted the cache, restarted Emacs, still the same Quicklisp issue x-P
20:37:12
phoe
do you have the alexandria asd file anywhere in ~/quicklisp/dists/quicklisp/software/?
20:38:24
contrapunctus
phoe: there's a /home/anon/quicklisp/dists/quicklisp/software/alexandria-20200925-git/alexandria.asd
4:22:45
beach
I guess in the spirit of the first example, I should have written (let ('5) (let (#'quote) (+ . #'6)))
4:25:47
no-defun-allowed
SLIME would print the lambda list of a mapping function I wrote as #'SEQUENCE.
4:59:09
beach
no-defun-allowed: That's a very good example of why I want something better than Emacs for writing Common Lisp code.
5:00:39
moon-child
that doesn't seem like a fundamental limitation of emacs though, only an incidental result of slime's implementation; no?
5:09:01
fiddlerwoaroof
It's fundamentally ambiguous whether the intention here is to print code or a list, as far as I can see
5:10:19
beach
One could, for example, show the characters in the source code that defined the item to be printed.
5:10:35
beach
Then you would get the same representation as the programmer wanted when the code was written.
5:11:42
fiddlerwoaroof
Yeah, that doesn't help when you're formatting the output of MACROEXPAND-1, though
5:12:47
fiddlerwoaroof
I use tools like emacs' macrostep expander quite a bit when I'm trying to figure out what a macro does
5:13:00
beach
Perhaps I am generalizing too much, but I almost never look at the result of a macro expansion.
5:13:48
beach
I see macros the say I see function, i.e., as abstractions. Only when I write the macro itself would I be interested in how it expands.
5:14:53
fiddlerwoaroof
When I decide that a macro was a bad idea, I usually MACROEXPAND-1 and replace the source with the expansion
5:15:39
beach
This is one reason why I made a rule that SICL macros should do a lot of syntax checking, so that conditions would be shown in terms of the macro call, rather than in terms of its expansion.
5:20:05
fiddlerwoaroof
I think if you continue down that route, you end up writing macros that expand to CLOS objects
5:23:00
beach
Not sure what you mean by "CLOS object", but if you mean "standard object" then that would be some very useless macros, since those are self-evaluating.
5:24:04
beach
... unless you implementation uses standard objects for conses and symbols, of course.