Hi,
I am writing a swank server for clojure, and for various reasons, not least of which the frequent updates to SLIME, the versions of slime.el used to connect are usually somewhat old.
The clojure swank server could easily support multiple versions of the slime protocol, making it less painful to set up for the many emacs newbies in the clojure world, but to do so would require knowledge of the slime protocol version implemented in slime.el.
Would a change in the swank:connection-info message to include slime-protocol-version be a possibility?
(swank:connection-info "20110501")
This obviously doesn't allow retroactive support of old slime versions, but would provide a path to doing so in the future.
* Hugo Duncan [2011-05-18 17:22] writes:
Hi,
I am writing a swank server for clojure, and for various reasons, not least of which the frequent updates to SLIME, the versions of slime.el used to connect are usually somewhat old.
The clojure swank server could easily support multiple versions of the slime protocol, making it less painful to set up for the many emacs newbies in the clojure world, but to do so would require knowledge of the slime protocol version implemented in slime.el.
Would a change in the swank:connection-info message to include slime-protocol-version be a possibility?
(swank:connection-info "20110501")
This obviously doesn't allow retroactive support of old slime versions, but would provide a path to doing so in the future.
Sounds reasonable. Maybe we should rename the first event and call it (swank:configure :version "20110501"). Possibly adding more parameters, like :encoding, in the future. Would that be OK?
Helmut
On Sun, 22 May 2011 06:20:39 -0400, Helmut Eller heller@common-lisp.net wrote:
Sounds reasonable. Maybe we should rename the first event and call it (swank:configure :version "20110501"). Possibly adding more parameters, like :encoding, in the future. Would that be OK?
Sounds good to me. Having an explicit encoding parameter sounds like it could help flag encoding mismatch issues.