freenode/#lisp - IRC Chatlog
Search
16:15:39
mfiano
yeah, i had thought it is where i found a particular article, but it turned out to be one of the other domains.
16:17:26
mfiano
XachX: also, i request that sly follow up article, or at an idea of where you are now :)
17:24:53
shka_
you may perhaps try to use some generator like SWIG, but no idea how hard or easy this will be
18:14:52
emaczen
fe[nl]ix: I was getting strange integers and am pretty sure I didn't do it correctly then
18:28:28
emaczen
phoe_: I don't like the idea of writing to a file and then reading from it, but maybe it is fast enough
18:42:46
emaczen
_death: is the idea that I can still write code in terms of files but it will still use RAM?
18:44:55
_death
that's not shared memory, but you can also do that using a tmpfs mount (e.g., /tmp or /var/tmp on some distributions)
19:08:56
phoe_
tell hunchentoot to output whatever proper HTTP headers it should output, give me the socket stream, and just (loop for jpeg in jpegs do (print-sequence jpeg stream))
20:57:32
jmercouris
can someone explain to me the message in the topic: the #1=(programmable . #1#) programming language
20:59:40
pjb
#1=(programmable . #1#) === #1=(programmable . (programmable . #1#)) === (programmable programmable . #1#) === (programmable programmable programmable . #1#)…
20:59:51
phoe_
in (#1=(a . b) (a . b) #1#), the result is an alist that looks like ((a . b) (a . b) (a . b))
21:02:30
jmercouris
So the joke is that lisp is the #1 programmable language because it can be programmed?
21:03:09
jmercouris
phoe_: sure, GNUS is also not a joke, but it's kinda a joke, you know what I mean?
21:03:28
phoe_
you can program the language and then you can program the programming of the language
21:03:57
Shinmera
I feel like explaining the topic is kind of ruining the beauty of it. It was a genuinely nice surprise when I realised what it meant on my own as I learned lisp.
21:04:26
jmercouris
Shinmera: I still think it's pretty cool, I just didn't know that syntax, didn't really ruin anything for me
21:05:10
pjb
Rather, try: (loop with *print-circle* = nil for *print-length* from 1 to 10 do (print '#1=(programmable . #1#)))
21:05:42
pjb
_death: *print-length* is useless in your case if you have *print-circle* true! (which you should have in your rc file by default).
21:06:28
_death
pjb: no, I keep it at nil, because I don't usually want #n# shown for simple shared structure
21:07:25
_death
on the other hand, a moderate bound on print-length may be a good idea (I thought about it before, but didn't get a chance to try)
21:10:10
jmercouris
Shinmera: with so many projects, how do you keep them clear in your head? how do you remember what you were working on last in a given project?
21:10:58
Shinmera
jmercouris: Usually I don't, because I finish them so I don't have to work on them any more aside from bug fixes.
21:20:23
Shinmera
For those that are too large to finish quickly I just organise code very clearly and keep ideas recorded in issues or on my trello.
21:22:21
jmercouris
There's so many configuration possibilities, and you can infinitely tweak your config, but actually is not a good way to start imo
21:24:30
jasom
someone tell me what I'm doing wrong: (extern-alien "write" (function long (* void) long))
21:36:53
Cthulhux
libnotify seems to be the consensus about how to display notification toasts on linux
21:38:30
Shinmera
Sure, and you can't display toasts on a WM without a notification handler (even more common)
21:39:37
Shinmera
You could do your own thingy to display notifications with simple frameless windows.
21:40:25
Shinmera
If you're using Qtools, QUI has that ready for you :) https://github.com/Shinmera/qtools-ui/blob/master/notification.lisp
21:41:49
Shinmera
Haha, yeah. Won't get low deps with Qt. At least deployment is handled for you and mostly "just works" from my own tests.
23:10:14
pjb
emaczen: errno is not a variable. It may be a macro expanding to some complex expression, like, accessing some thread specific attribute.
0:51:59
jasom
ultra fast "yes" implementation in under 140 characters: https://www.reddit.com/r/lisp/comments/75wla9/writing_a_fast_yes_program_that_can_fit_in_a_tweet/doa6gut/
2:37:15
pillton
jmercouris: Be aware that the standard requires logical pathnames to be all uppercase.
2:37:23
specbot
Syntax of Logical Pathname Namestrings: http://www.lispworks.com/reference/HyperSpec/Body/19_ca.htm
2:59:49
jmercouris
pillton: I found it such an obtuse syntax, but I didn't want to change the code that was using it
3:04:53
pillton
It is my understanding that it was defined at a time when there where no clear "winners" in terms of pathname syntax or file system functionality.
3:22:52
jmercouris
iqubic: I was having trouble just extending the path, the syntax totally threw me off, that's all