newline incompatability on Unix vs. Windows (CMUCL)
From: Christopher C. Stacy (cstacy_at_news.dtpq.com)
Date: 04/22/04
- Next message: Barry Margolin: "Re: Does LETF lead to an identity crisis?"
- Previous message: Joe Marshall: "Re: Does LETF lead to an identity crisis?"
- Next in thread: Barry Margolin: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Reply: Barry Margolin: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Reply: Tim Bradshaw: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 22 Apr 2004 17:45:34 GMT
CMUCL barfs on FORMAT control strings like:
(format nil "SELECT ~A FROM ~A ~
WHERE THIS SOURCE FILE ~
ORIGINATED IN emacs ON windows")
Any suggestions?
Maybe there's something I should be doing in Emacs
to control the EOF encoding better.
I think Lispworks, which is the Windows side,
is tolerant of either newline encoding.
I wish CMUCL was, too, by the way.
- Next message: Barry Margolin: "Re: Does LETF lead to an identity crisis?"
- Previous message: Joe Marshall: "Re: Does LETF lead to an identity crisis?"
- Next in thread: Barry Margolin: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Reply: Barry Margolin: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Reply: Tim Bradshaw: "Re: newline incompatability on Unix vs. Windows (CMUCL)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]