help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: slime and lisp buffer encoding


From: Eric
Subject: Re: slime and lisp buffer encoding
Date: Fri, 7 Aug 2009 03:23:38 -0700 (PDT)
User-agent: G2/1.0

On Aug 7, 5:52 pm, Eric Abrahamsen <gir...@gmail.com> wrote:
> Hi,
>
> I'm using Emacs and slime to do a bit of hunchentoot (lisp web server)  
> development, and I'm running into an encoding problem. I don't know  
> which of the links in the chain is causing the problem, so I hope  
> someone here will see what's going...
>
> Basically, using hunchentoot (with cl-who for html templating)  
> involves writing the html templates directly into the source code, and  
> I'm discovering that I can't type utf-8 text into these source files.  
> Compiling a defun with unicode in it results in an encoding error (I  
> believe thrown by slime as the defun gets sent to the repl).
>
> I have set everything I can set (file, keyboard, subprocess IO) to  
> utf-8-unix. The weird thing is, I can type a Latin accented a (à) into  
> the source without trouble. Hunchentoot seems to use a CONTENT-TYPE of  
> iso-8859-1 by default, in which case the à shows up fine in the  
> browser. If I set content type to utf-8, my browser garbles the à. So  
> my lisp strings must be encoded as iso-8859-1, but how did they get  
> that way? And how do I make them utf-8?

I'll answer my own question: They got that way because iso-8859-1 is
the default string encoding for OpenMCL. Altering inferior-lisp-
program to add the option "-K utf-8" after the executable results in a
lisp that runs in utf-8 by default. Apologies for the noise.

E

>
> I'm using emacs CVS, slime 3.0 alpha, Mac Leopard, ccl version 1.2.  
> Hope someone's got a pointer (if only to the slime or hunchentoot  
> mailing lists).
>
> Thanks,
> Eric



reply via email to

[Prev in Thread] Current Thread [Next in Thread]