[slime-devel] Slime and remote SBCL unicode issue

[Tayssir John Gabbour]

Hi,

I have a problem when using unicode while slime-connect'ed to a remote sbcl. For
example, (princ #\em_dash) kills my slime connection, and the message on the
remote lisp is a huge backtrace, including:


DISPATCHING: (:EMACS-REX (SWANK:LISTENER-EVAL "(princ #\\em_dash)
") "COMMON-LISP-USER" :REPL-THREAD 2)
DISPATCHING: (:WRITE-STRING "\x2014")
WRITE: (:write-string "\x2014")
;; Event history end.
;; Backtrace:
;; Connection to Emacs lost. [
;;  condition: Unable to display error condition: #<SB-SYS:FD-STREAM for "a
constant string" {C0EECB1}> is closed.
;;  type: SB-INT:STREAM-ENCODING-ERROR
;;  encoding: NIL style: :SPAWN dedicated: NIL]


However, this problem does not occur when running slime using M-x slime (as
opposed to M-x slime-connect). Nor does it occur when running SBCL on the
commandline.


My platform:
    Slime - new cvs version on both ends
    SBCL  - 1.0.5
    Emacs - 21.4.1
    OS    - Debian Gnu/Linux 2.6.20.1
    slime-net-coding-system - 'utf-8-unix


Any ideas? Does this look vaguely familiar to anyone?


Thanks,
Tayssir