Hi.
My current configuration is Windoze/Emacs-21.3/Clisp-2.35 native (not the cygwin port, which is much slower) and it seems that a recent fix in swank-clisp.lisp in function find-encoding is not "portable". In fact, it is compatible with Clisp-2.35-Unix-flavor (MacOSX and Cygwin included) but not with the native W32 version which lacks some encodings (only 85 vs 121 for the unix version, to be accurate).
I include a patch that solves the problem for me (by not using the inexistant symbol directly) ant should also work for those using the japanese encoding on Clisp versions supporting it.
Laurent.
--- swank-clisp.lisp.bak 2005-09-14 09:16:12.523260100 +0200 +++ swank-clisp.lisp 2005-09-14 09:19:14.141146000 +0200 @@ -123,7 +123,7 @@ :line-terminator :unix)) (:utf-8-unix (ext:make-encoding :charset 'charset:utf-8 :line-terminator :unix)) - (:euc-jp-unix (ext:make-encoding :charset 'charset:euc-jp + (:euc-jp-unix (ext:make-encoding :charset (find-symbol "EUC-JP" :charset) :line-terminator :unix))))
(defimplementation accept-connection (socket
* VAUCHER Laurent [2005-09-14 09:23+0200] writes:
I include a patch that solves the problem for me (by not using the inexistant symbol directly) ant should also work for those using the japanese encoding on Clisp versions supporting it.
Fixed in CVS. Thank you for the note.
Helmut.