[slime-devel] Another small request...

[Paul Bowyer]

On 04/03/2011 04:00 PM, Paul Bowyer wrote:
> slime-devel:
>
> As I'm working with Slime and learning Lisp, I occasionally copy/paste
> code examples into 'somefile.lisp' for compiling/loading to test from
> the Slime REPL.
>
> Usually when extended characters show up in Emacs after pasting some
> code, I'm able to notice them and overwrite them with the correct
> characters, but I recently ran into a situation where an extended
> character (0xE28099) showed up that I was unable to discern visually
> (looked like a ') and when I tried to compile the file the slime
> connection was broken and I received
>
> "Lisp connection closed unexpectedly: connection broken by remote peer"
>
> which I was able to correct by restarting Slime.
>
> However, I had to examine the lisp source file in a hex editor (vim also
> worked) to discover which character was the offender. Is there a way set
> up Slime (or Emacs) so extended characters are identified and marked
> (even when they don't appear visually different than ascii)?
>
> Thanks
>
> pbowyer
>
>
> _______________________________________________
> slime-devel site list
> slime-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/slime-devel
>

After I sent the above message, I discovered that if I moved the input 
point through the source file, when I reached the offending character, I 
got lots of information showing up in the mini buffer of Emacs telling 
me of the unsuitability of extended characters. I guess I'll have to 
make it a practice of scrolling through the text after pasting code 
snippets into source files.

Sorry for the noise,

pbowyer