<luis>
fiddlerwoaroof: in a nutshell, my idea is make send-event-to-emacs (or some shorter name) available to contribs, as well as let them add methods to a new handle-events generic functions (perhaps with a macro for taking care of event destructuring, though plain defmethod would be best, I think)
StephanL` has quit [Ping timeout: 268 seconds]
makomo has quit [Ping timeout: 245 seconds]
makomo has joined #slime
aerique has quit [Ping timeout: 268 seconds]
<luis>
fiddlerwoaroof: also, I'm thinking it'd make sense to split the swank package in two, where one is for contribs to use and another is for end-users (create-server, etc)
anamorphic has joined #slime
makomo has quit [Ping timeout: 246 seconds]
scymtym has quit [Ping timeout: 268 seconds]
<fiddlerwoaroof>
cool
<fiddlerwoaroof>
I'm not entirely certain about the generic function idea
<fiddlerwoaroof>
The nice thing about the way swank is written today is that event handling looks very similar in both Common Lisp and elisp
anamorphic has quit [Quit: anamorphic]
anamorphic has joined #slime
scymtym has joined #slime
scymtym has quit [Client Quit]
scymtym has joined #slime
anamorphic has quit [Quit: anamorphic]
anamorphic has joined #slime
anamorphic has quit [Quit: anamorphic]
anamorphic has joined #slime
anamorphic has quit [Client Quit]
anamorphic has joined #slime
<luis>
fiddlerwoaroof: I guess both approaches (hooks or generic function) can be hidden behind the (define-event-handler :foo (x y z) ...) macro, so it's a bit of an implementation detail.
<luis>
but I see your point.
anamorphic has quit [Quit: anamorphic]
<luis>
fiddlerwoaroof: one advantage of the hook approach is that you can handle multiple events in one handler with dcase
<fiddlerwoaroof>
Yeah, and it's really easy to figure out the emacs code, because it's slime-dcase