![](https://secure.gravatar.com/avatar/f5267d15dab3a23715fd09ee84a7886e.jpg?s=120&d=mm&r=g)
Helmut Eller <e9626484@stud3.tuwien.ac.at> writes:
Marco Baringer <mb@bese.it> writes:
*new-connection-hook* passes the connection struct to emacs-connected which expects a stream argument. something has to be changed. should emacs-connected be changed to take a connection object or should the elements in *new-connection-hook* be passed the stream?
Neither variant is very appealing, but passing the stream is probably easier for now. The current package organization makes it difficult to access struct slots in the backend.
idea: we could put (lambda (connection) (emacs-connected (connection.socket-io connection))) on *new-connection-hook* instead of putting emacs-connected directly. wouldn't this do it? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen