kevingal has quit [Remote host closed the connection]
mindCrime_ has joined #commonlisp
random-nick has quit [Ping timeout: 244 seconds]
killsushi has quit [Quit: Leaving]
tyson2 has quit [Ping timeout: 252 seconds]
Lycurgus has quit [Quit: Exeunt]
unyu has quit [Quit: WeeChat 3.1]
terpri is now known as robin
<drmeister>
pjb: What does that bring to the table? It's built on bordeaux thread destroy-thread?
<drmeister>
Not challenging - just curious.
sander has quit [Quit: So long! :)]
sander has joined #commonlisp
dsk has joined #commonlisp
GreaseMonkey has joined #commonlisp
waleee has quit [Ping timeout: 272 seconds]
contrapunctus has left #commonlisp [#commonlisp]
azimut_ has joined #commonlisp
azimut has quit [Ping timeout: 252 seconds]
contrapunctus has joined #commonlisp
<pjb>
drmeister: indeed. They're repl "commands", ie, functions intended to be called interactively from the REPL. list-threads displays the list of threads. kill-thread calls list-threads, and let the user select a thread to kill it.
<pjb>
drmeister: this way, I don't have to remember how one kills a thread (when all I want to do is to kill blocked threads I forked from slime).
<pjb>
drmeister: of course, when you run slime/swank, there's also M-x slime-list-threads RET and k (slime-thread-kill) …
<pjb>
drmeister: sometimes, a what a function brings, is only its name. You didn't ask "How does one destroy a thread?", but "How does one kill a thread?", as any normal person woul do. So naturally, what is needed is a kill-thread function, not a destroy-thread function. Try (apropos "KILL") !
<pjb>
drmeister: that's also what my tools/quicklisp.lisp provides, with a bunch of (quick-…) quicklisp commands. Most are just renaming or thin layers on quicklisp stuff. Some people have really twisted naming minds…
tyson2 has joined #commonlisp
unyu has joined #commonlisp
tyson2 has quit [Ping timeout: 252 seconds]
Alfr has quit [Remote host closed the connection]
<beach>
Good morning everyone!
<jcowan>
Some people don't like talking about killing things much.
<Josh_2>
Some people do
Josh_2 has quit [Remote host closed the connection]
<dsk>
euthanize-thread
<drmeister>
Does anyone use pytorch?
Lord_of_Life_ has joined #commonlisp
<drmeister>
Or even better the C++ torch API?
Lord_of_Life has quit [Ping timeout: 265 seconds]
Lord_of_Life_ is now known as Lord_of_Life
<drmeister>
pjb: Thank you.
<drmeister>
I'm killing a bordeaux thread by pressing a button in a browser.
<drmeister>
I have multiple of these workers running in parallel and I'm monitoring them and occasionally I have to stop them and make changes and then restart them.
nick3000 has quit [Read error: Connection reset by peer]
Cymew has joined #commonlisp
rusua has joined #commonlisp
mindCrime_ has quit [Ping timeout: 252 seconds]
mindCrime_ has joined #commonlisp
mindCrime_ has quit [Ping timeout: 245 seconds]
v88m has quit [Ping timeout: 272 seconds]
Oladon has quit [Quit: Leaving.]
Inline has quit [Quit: Leaving]
frgo has quit [Remote host closed the connection]
frgo has joined #commonlisp
Inline has joined #commonlisp
tyson2 has joined #commonlisp
random-nick has joined #commonlisp
McParen has joined #commonlisp
taiju has quit [Ping timeout: 264 seconds]
taiju has joined #commonlisp
<McParen>
Hello, after a few weeks of Libera, can anybody compare the activity levels here and at freenode?
<McParen>
Is #lisp on freenode still the most active channel?
<MichaelRaskin>
#lisp on Freenode is dead
<McParen>
What about the two new chans here on libera, #lisp and #commonlisp? Is common lisp discusses here more actively or in #lisp?
<MichaelRaskin>
Well, the aim is to have #lisp close to old ##lisp and #commonlisp be about Common Lisp.
<McParen>
I only occasionally lurk, but for some reason do not want to monitor several channels to find out where the discussions have moved.
<MichaelRaskin>
It seems to drift in that direction
<McParen>
Has that been the case, that common lisp topics actually are kept to #commonlisp, or are they still discussed more in #lisp?
<MichaelRaskin>
Sometimes some people ask a question in #lisp which is mostly about Common Lisp. But I think most of the discussion in #lisp are such that Common Lisp and Scheme and Clojure answers are all appreciated
<phoe>
#lisp has some CL discussions now and then
<phoe>
but most of them happen in #commonlisp
<McParen>
Ok, that is what I wanted to know, thanks.
knusbaum has joined #commonlisp
knusbaum has quit [Remote host closed the connection]
yewscion has joined #commonlisp
dsk has quit [Ping timeout: 268 seconds]
seok has joined #commonlisp
<edgar-rft>
McParen: basically freenode #lisp moved to Libera.Chat #commonlisp and freenode ##lisp moved to Libera.Chat #lisp. The reason for this is that on freenode many newbies joined #lisp and started to ask Scheme questions without reading the channel topic, so now Libera.Chat #lisp is for *all* Lisps and Libera.Chat #commonlisp is for Common Lisp only.
<ldb>
would it be easy to a "keyboard macro" feature to CLIM based applications?
<ldb>
*add a
yewscion has quit [Ping timeout: 244 seconds]
McParen has left #commonlisp [#commonlisp]
contrapunctus has left #commonlisp [#commonlisp]
contrapunctus has joined #commonlisp
domovod has quit [Quit: WeeChat 3.1]
knusbaum has joined #commonlisp
Bike has joined #commonlisp
dsk has joined #commonlisp
<beach>
ldb: Can you give some more detail about what you want?
knusbaum has quit [Remote host closed the connection]
<ldb>
beach: For example, in a interactive prompt of CLIM, the user can store some predefined actions by recording them, and replay these actions when needed
<beach>
The easiest way to do that is just to click on an previous interaction. Every interaction is a presentation that can be re-executed by a click.
<ldb>
Is it possible to re-executed multiple interactions simultaneously?
<beach>
I don't think so, no.
* ldb
if it does not fit into the design of CLIM I guess I can add some script interface then.
aleamb has quit [Quit: bye]
contrapunctus has left #commonlisp [#commonlisp]
contrapunctus has joined #commonlisp
<jackdaniel>
that would be the editing substrate feature (i.e drei) - keyboard macros that is
ldb has quit [Ping timeout: 272 seconds]
<jackdaniel>
perhaps seis subclass could do that too
<jackdaniel>
i.e we already do dead key merging there
<jackdaniel>
so there are a few possible abstractions where you could implement that
<pjb>
Well, you see, somebody deleted the ILU Cliki page, therefore lowering awareness, and leading to the decay of ftp.parc.xerox.com which is now dead. Good job!