14:17 <luis> fiddlerwoaroof: I hadn't noticed that events didn't map directly/automatically to swank messages.

17:56 <fiddlerwoaroof> luis: yeah, that surprised me a bit too

21:38 <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.

21:38 <luis> I think I'll pick door #3.

21:45 <Shinmera> luis: https://www.youtube.com/watch?v=sdQ11fTRpCg

21:50 <luis> So silly. 🤦‍♂️ :-)

22:04 <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.

22:09 <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.

22:46 <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.

23:02 <luis> https://github.com/luismbo/slime/tree/split-dispatch-event is all I've got for tonight.

23:03 <luis> fiddlerwoaroof: I think this is proof-of-concept that we can simplify event handling quite a bit.