[slime-devel] clisp without unicode patch

Hoehle, Joerg-Cyril Joerg-Cyril.Hoehle at t-systems.com
Fri Jan 20 17:58:19 UTC 2006

Helmut Eller wrote:

>The user has to choose an encoding that actually works
I had hoped for auto-detection, or at least reasonable defaults and consistent settings.
E.g. I found a message in the *inferior-lisp* buffer ("event-history end") saying
that iso-8859-1 was used.
However, the buffer's mode line says "u". Same for the slime-repl and *slime-events* buffers.  Same for many other buffers in Emacs (e.g. Dired), while Lisp source buffers mostly say "--", i.e. ASCII.

.slime-history.eld says -*- utf-8-unix (but so far there's only ASCII therein).

This is Emacs-21.4 on a Ubuntu Breezy i386 with the default clisp-2.35 (not self compiled) -- with #+UNICODE.

How comes?  Is that 1/3 a bug-report?

>because the packet length field isn't interpreted
>correctly and the payload of the packet will be truncated
I wasn't aware slime is sending packets. I thought it's all Lisp data, readable with READ :)

I think it's then ok to modify the patch to assert :iso-8859-1 on a non unicode clisp.  And let the user figure out how to set this???

	Jorg Hohle.

More information about the slime-devel mailing list