[Openmcl-devel] slime and unicode: Lisp connection closed unexpectedly: connection broken by remote peer
Tobias C. Rittweiler
tcr at freebits.de
Mon Mar 8 16:42:58 UTC 2010
Leo <sdl.web at gmail.com> writes:
> On 2010-03-08 15:08 +0000, Tobias C. Rittweiler wrote:
>>> I guess it may be a bug in slime. For example, when I run 'ccl64 -K
>>> utf-8' in terminal and connect to it from emacs:
>>> (defparameter language '日本語)
>>> will disconnect slime right away.
>>> With inferior lisp, however, it seems to work as noted in ccl wiki.
>>> Everything else works for me.
>> Try HEAD and paste the debugging output you get in *inferior-lisp*.
> With HEAD both ccl and slime, and 'Emacs -q -l slime-test.el'.
> 1. swank server is started in the terminal.
> 2. slime-connect to the server
You have to pass the right :coding-system to CREATE-SERVER like
(swank:create-server :coding-system "utf-8-unix")
Or set swank:*coding-system* to that value, e.g. in your ~/.swank.lisp.
> 3. (defparameter language '日本語)
> The text on the terminal:
> The event log buffer:
> "COMMON-LISP-USER" t 1)
> (:pid 12837 :style :spawn :encoding
> (:coding-system "iso-latin-1-unix"
> :external-format "#<EXTERNAL-FORMAT :ISO-8859-1/:UNIX #x3020008B5EFD>")
Here we see that latin-1 rather than an UTF-8 encoding is actually used
on the server.
That is because SWANK:*CODING-SYSTEM* defaults to "iso-latin-1-unix".
More information about the Openmcl-devel