*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?
-- -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
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.
Helmut.
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 Baringer mb@bese.it writes:
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?
.user-io needs to be flushed, not .socket-io. Otherwise it's fine.
Helmut.
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?
That was a braino. Now it passes the user-io struct.
OpenMCL will have been temporarily broken by the previous version. Can someone confirm that it works now? (If not SLIME won't start.)
P.S., if anyone has a machine that can run the latest OpenMCL and that I could ssh into at random times to do small SLIME tests then a login would be much appreciated!
-Luke
Luke Gorrie luke@bluetail.com writes:
OpenMCL will have been temporarily broken by the previous version. Can someone confirm that it works now? (If not SLIME won't start.)
ok, works perfectly.
P.S., if anyone has a machine that can run the latest OpenMCL and that I could ssh into at random times to do small SLIME tests then a login would be much appreciated!
i'm behind a firewall, which would require some weird ssh tunnelling and i connect and disconnect at random times, other than that i'd be happy to give you a login. consider me your "if all else fails" solution.
-
Helmut Eller -
Luke Gorrie -
Marco Baringer