Abort when unicode is used #14

Closed
leoliu opened this Issue Jan 4, 2012 · 3 comments

Comments

Projects
None yet
3 participants
@leoliu

leoliu commented Jan 4, 2012

Try entering the following in slime-repl:

"你好".length

after that all communication between slime and swank is broken. The same thing happens when the return value from swank contains unicode. For example, I was trying the example:

$(".sitetable a.title").map(function(n) { return (n + 1) + ". " + $(this).text(); }).get().join("\n")

and reddit.com today contains this heading (note the two unicode chars at the end):

I just explained memes to my uncle. This was his first one ಠ_ಠ (qkme.me)

The error looks like this: http://paste.pocoo.org/show/529755

@jonnay

This comment has been minimized.

Show comment
Hide comment
@jonnay

jonnay Feb 9, 2012

Member

I don't get the error, but I explicity set all buffers to utf-8. What is the value of your buffer-file-coding-system? ("C-h v buffer-file-coding-system") What happens when you try to set it to UTF-8, same problem?

Member

jonnay commented Feb 9, 2012

I don't get the error, but I explicity set all buffers to utf-8. What is the value of your buffer-file-coding-system? ("C-h v buffer-file-coding-system") What happens when you try to set it to UTF-8, same problem?

@leoliu

This comment has been minimized.

Show comment
Hide comment
@leoliu

leoliu Feb 18, 2012

I just tried (prefer-coding-system 'utf-8) in a newly-started emacs and re-did the experiment. The problem persists.

leoliu commented Feb 18, 2012

I just tried (prefer-coding-system 'utf-8) in a newly-started emacs and re-did the experiment. The problem persists.

ivan4th added a commit that referenced this issue Feb 22, 2012

Fixed UTF-8 handling (#14).
Some time ago SLIME wire protocol was changed to specify
number of bytes in the header, and here we were still counting
chars which was leading to protocol errors.
@ivan4th

This comment has been minimized.

Show comment
Hide comment
@ivan4th

ivan4th Feb 22, 2012

Member

There was indeed a compatibility problem with recent & semi-recent SLIME versions. After upgrading to latest SLIME and fixing connection-info stuff, I've noticed that problem, too. Fixed it now, just upgrade to latest SLIME and have fun.

Member

ivan4th commented Feb 22, 2012

There was indeed a compatibility problem with recent & semi-recent SLIME versions. After upgrading to latest SLIME and fixing connection-info stuff, I've noticed that problem, too. Fixed it now, just upgrade to latest SLIME and have fun.

@ivan4th ivan4th closed this Feb 22, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment