luis changed the topic of #slime to: SLIME, the Superior Lisp Interaction Mode for Emacs | https://common-lisp.net/project/slime | https://irclog.tymoon.eu/freenode/%23slime | https://irclog.whitequark.org/slime
makomo has quit [Quit: WeeChat 2.2]
_whitelogger has joined #slime
makomo has joined #slime
scymtym has quit [Ping timeout: 246 seconds]
scymtym has joined #slime
antoszka has quit [Quit: WeeChat 2.1]
antoszka has joined #slime
scymtym_ has joined #slime
scymtym has quit [Ping timeout: 268 seconds]
scymtym_ has quit [Ping timeout: 268 seconds]
scymtym_ has joined #slime
scymtym_ has quit [Ping timeout: 250 seconds]
scymtym_ has joined #slime
scymtym_ has quit [Remote host closed the connection]
makomo has quit [Ping timeout: 268 seconds]
scymtym has joined #slime
<luis> fiddlerwoaroof: I hadn't noticed that events didn't map directly/automatically to swank messages.
scymtym has quit [Ping timeout: 250 seconds]
<fiddlerwoaroof> luis: yeah, that surprised me a bit too
scymtym has joined #slime
makomo has joined #slime
<luis> You've entered the OSS break room. There three doors: work on breakpoints / fix the test suite on Emacs 25+ / help fiddlerwoaroof with proper swank dispatching.
<luis> I think I'll pick door #3.
<luis> So silly. 🤦‍♂️ :-)
<luis> So, slime-dispatch-event only gets inbound events whereas swank::dispatch-event gets both inbound and outbound events. That's the first unexpected difference. Also, it seems like some of the inbound events might actually be triggered by other parts of swank.
<luis> It's not clear to me why we're handling both inbound and outbound events in the same function. I'm inclined to start by splitting those up and see what bad things happen.
<luis> Well, it's forcing me to learn a bit more about how swank swings events around and that's not a bad thing per se. I even have a seemingly working sldb.
<luis> fiddlerwoaroof: I think this is proof-of-concept that we can simplify event handling quite a bit.