freenode/#lisp - IRC Chatlog
Search
1:22:48
aeth
I think #\ is standard, too, but obviously it's way less readable (I mean, just look at my line, when I didn't put it in quotes like you did)
1:26:56
no-defun-allowed
Speaking of which, do people have any strategies for making (foo bar #\)) look less awkward?
2:13:07
sjl
Xach: is there a way to find the git/hg commit hash for a particular library in a quicklisp dist?
2:13:43
sjl
I see a "content-sha1" in releases.txt but that doesn't appear to be the commit hash (I'm guessing it's a SHA of the tarball or something)
4:21:20
beach
So I take it nobody wants to appear in the Acknowledgments section of this paper: http://metamodular.com/SICL/representing-method-combinations.pdf
6:26:31
no-defun-allowed
It appears that this function definition (rather, the documentation string) prevents C-c C-c from working correctly: https://pastebin.com/h8sHNTzf
6:31:15
no-defun-allowed
That appears to compile from (with-locked-box ...) in the documentation string wherever I C-c C-c from, which fails spectacularly.
6:32:04
trittweiler
the answer is most likely "don't write docstrings like that", i.e. intend inner code blocks by at least 1 space
6:57:03
beach
no-defun-allowed: You can use the trick with #.(format nil "...") so that in the format control you can ignore indented lines.
6:57:38
beach
No version of the paper. Thanks to MetaYan and slyrus for the feedback: http://metamodular.com/SICL/representing-method-combinations.pdf
7:57:54
splittist
no-defun-allowed: https://www.gnu.org/software/emacs/manual/html_node/emacs/Left-Margin-Paren.html
11:39:04
p_l
beach: well, it would be nice to appear - but that requires actually having done something for it to happen ;)
12:17:27
phoe
beach: about CCL, "Instead it defines an info vector (disguised as a structure)" - CCL tends to do that a real lot. From what I have noticed, a lot of internal structures in CCL are actually tagged vectors, where the tag tells CCL what kind of a structure that is.
12:22:09
phoe
p_l: nope, it's a different trick that CCL uses. The resulting object still prints like a structure type and has its own distinct type.
12:25:10
phoe
(defstruct (foo (:type vector)) a b c) (type-of (make-foo)) ;=> (SIMPLE-VECTOR 3) on SBCL
12:34:36
phoe
There are things called ivectors and gvectors in CCL that are tagged like I described up above - but, amusingly, CCL's method-combination-info objects are neither of them
12:34:38
montaropdf
I have some strange configuration problem with my common lisp environement. ~/common-lisp/ is not in the asdf registry and some packages seems missing from quicklisp.
12:36:52
montaropdf
Message from quicklisp: You already have the latest version of "quicklisp": 2019-12-27.
12:37:18
montaropdf
Message from the client: The most up-to-date client, version 2020-01-04, is already installed.
12:39:02
phoe
https://github.com/quicklisp/quicklisp-projects/search?utf8=%E2%9C%93&q=informatimago&type= gives me nothing.
12:39:44
phoe
montaropdf: quicklisp/quicklisp-projects on github is the ultimate source of information for what is included in QL.
12:43:05
phoe
on my machine, asdf:*central-registry* ;=> (#P"/home/phoe/.roswell/lisp/quicklisp/quicklisp/")
12:44:02
phoe
maybe that's the cause - if you've installed QL, it likely is set to ~/quicklisp/local-projects/
12:44:36
montaropdf
I just check now and look what I have found: #P"/home/roland/quicklisp/quicklisp/"
12:50:58
montaropdf
So, I will add ~/common-lisp/ to the registry from .sbclrc, seems the best to do.