freenode/#lisp - IRC Chatlog
Search
22:11:36
stylewarning
i was hoping there'd be a nice interface out there for managing child processes and the like
22:12:52
White_Flame
there are libs for non-forked process management, I think UIOP contains some of that, and some trivial-*
22:16:26
White_Flame
I have no idea what devils lie in the details of the interaction between fork and ffi
22:17:25
Odin-
I would expect to tread carefully, because Common Lisp really doesn't make many concessions to the process model.
22:18:02
iAmDecim
so quick question. i've definitely had slime working on my macbook before. I just recently tried to start up a repl and I added (load "~/quicklisp/setup.lisp") to my init.el file and it's giving me void-function defpackage
22:18:52
White_Flame
that setup.lisp is for your common lisp startup (eg .sbclrc). it's not emacs lisp
22:19:24
White_Flame
there are quicklisp helpers to install all that for you; you shouldn't have to do it manually
22:19:58
iAmDecim
oh....ok. i took a wrong path. i'll go back. I know years ago I had to add something funny to give it the path. time to do some pruning
22:20:58
White_Flame
"The function ql:add-to-init-file will add code to do this to your init file automatically, so Quicklisp will load whenever your Common Lisp session starts."
22:27:42
jmercouris
what's a good way to capture stdout/stderror from a program not launched via terminal?
22:33:52
White_Flame
iAmDecim: slime-helper is when you get your lisp implementation, then quicklisp, then let ql install slime. If you already have slime, then you don't need the slime helper
22:53:17
pjb
minion: memo for jmercouris: stdout/stderr are directed to the same file descriptor as the parent process. So, what does the parent process do to them? (It may redirect them to /dev/null). Inside the child, you can reopen or dup them. What do you want to do?
23:01:18
iAmDecim
ok it's at least running but has anyone seen these warnings? https://pastebin.com/3cDZeUXu
23:06:08
iAmDecim
White_Flame: ahh..I bet I am. Checking...I just tried to reinstall slime since it's been years.
23:08:04
White_Flame
because there are some sb-fm internals that aren't matching, and you're running a newer sbcl version, there's probably an old version of slime
23:10:20
iAmDecim
yeah. i reinstalled slime. Restarting emacs just cut out a large portion of the errors...there's still one block. https://pastebin.com/HYRp0emK
23:11:02
iAmDecim
oh i see what you mean now....ok i'll play with that later. i bet i did install sbcl with brew and an older method.
23:11:23
iAmDecim
I'll play with this tonight. I really need to clean things up anyways on this laptop
23:35:48
amnesia1010
https://docs.google.com/forms/d/e/1FAIpQLSfg7UJRKrkI3OjOHWL4xI-murE4LpQjIxsiAhFdPEmtyLX3kg/viewform
0:09:19
vms14
(sb-bsd-sockets:socket-send *socket* (format nil "print STDERR 'meh';'as';~%") nil) => "as"
0:10:45
vms14
well atm is just perl evaluating whatever it founds from the socket and returning the results
0:12:00
vms14
just try, I suppose most lispers end using another language because lack of libraries or whatever in lisp
0:12:18
vms14
if the language you want to use has eval, you can just use sockets and make it eval whatever it reads
0:12:33
vms14
or predefine functions or whatever, and you can even return lists to the socket so lisp can eval them
0:13:18
vms14
I had the same stuff but calling the perl interpreter, which is slow, now with sockets will be much faster
0:18:45
no-defun-allowed
"I suppose most lispers end using another language because lack of libraries or whatever in lisp" What? Quite the opposite.
0:21:27
no-defun-allowed
And by "quite the opposite", I mean I haven't really written any big projects in any language since I picked up Lisp.
0:22:33
vms14
you can, and it's likely that being implemented in lisp they'll be "better" software than in the other languages
0:22:42
Odin-
vms14: Because in my experience using a Lisp FFI makes even C interfaces workable in interactive development.
0:23:15
no-defun-allowed
I'm not even trying to find them; both were within the first page of DuckDuckGo results for "common lisp {discord,telegram}"
0:31:50
vms14
(defparameter *socket-out-stream* (sb-bsd-sockets:socket-make-stream *connection* :element-type 'character :output t))
0:32:58
no-defun-allowed
All I can say is that it's a character output stream. What happens when you write-line to it?
0:33:06
vms14
it says it's not a byte stream with write-byte and not a character stream with the others
0:33:47
vms14
#<SB-SYS:FD-STREAM for "socket /home/vms/meh.oh" {1003DA8B13}> is not a character output stream.
0:36:00
no-defun-allowed
(usocket:socket-stream (usocket:socket-connect "127.0.0.1" 12345)) ; => a two way character stream
0:36:52
no-defun-allowed
Probably not, but it can probably get the stream from a socket created with SB-BSD-SOCKETS.
0:38:18
vms14
anyway I can write lines with sb-bsd-sockets:socket-send and read lines without having to worry on sizes to read
0:38:29
Thilastiko
Hello World! I am new to irc on emacs and am hoping to find out if theres a channel out there for newbies
0:49:42
no-defun-allowed
"LdBeth: you've been in a coma for 25 years" "oh, have they fixed the Riot client yet?" "lol no"