9 Nov
2004
9 Nov
'04
6:11 p.m.
Christophe Rhodes csr21@cam.ac.uk writes:
How odd.
To me, it seems that this bug has always been there, and I have no idea why we've only just started noticing it. (Clearly I don't do enough real work in slime). The problem arises in UTF-8 locales only, with slime's emacs end treating the first three bytes or so of a connection as text (rather than binary).
The attached patch fixes the problem at a certain cost in dynamic range of communications. Please advise if this is the desired solution, or if I/we need to do some more work.
Why do you need utf-8? Can't you use a unibyte coding system like iso-latin-1? I'd rather keep the complexity of multiple coding systems away from SLIME.
Helmut.