libera/#commonlisp - IRC Chatlog
Search
21:45:58
remexre
is there a "pathnames the good parts" cheatsheet? something like https://docs.python.org/3/library/pathlib.html#correspondence-to-tools-in-the-os-module but for lisp, i suppose
22:01:14
zyd
CIEL looks similar to what's been some people's approach to Emacs lately: building "distributions" or "starter" kits on top of plain Emacs. See Doom Emacs, Prelude, Spacemacs, Better Defaults and so on. These are all still Emacs except varying degrees of configuration done for you and sometimes quite complex ways of configuration that differ from plain Emacs (Spacemacs, Doom Emacs).
22:08:13
edwlan[m]
Why make a whole new bundle instead of saying "load this with quicklisp to get hash-table literals"
22:10:19
zyd
To provide someone with a set of "defaults" or a configuration they can use, I think. It's different than just recommending libraries, its a more opinionated set of usability features. That's how I think of it. Like, I wouldn't ever use it because of what you said. Same reason I use default Emacs. I can make my own configuration. Thing is, at least from my perspective, Emacs has bloomed in popularity due to things like this. Common Lisp could p
22:18:05
edwlan[m]
It is a bit annoying to work with, but you could develop some of its ideas into a nice successor to CL's pathnames
4:32:56
beach
Can someone explain this warning from SBCL: https://plaster.tymoon.eu/view/3739#3739 ?
4:35:29
beach
I guess I made some mistake, but I don't see it. Also, the message contains the name of a variable that is not very explicit.
5:35:42
mfiano
Can you see what the warning changes to if you return NIL or (VALUES) instead of NEW-VALUE?
5:36:54
mfiano
I don't think it is upset about the return value, but I would like to make sure first.
6:25:09
beach
Now, CLtL2 is freely available, but what are we allowed to do with the material? I am asking because it could be an excellent starting point for a language reference.