Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#555 SYSTEM::SET-STREAM-EXTERNAL-FORMAT fails on swank streams.

lisp error
closed-fixed
Sam Steingold
clisp (525)
5
2010-06-24
2010-06-24
No

I set my encodings in ~/.clisprc.lisp ie.:
(setf CUSTOM:*PATHNAME-ENCODING* (ext:make-encoding :charset CHARSET:ISO-8859-1 :line-terminator :UNIX))

It seems that when clisp is launched with slime/swank, the streams are changed, and set-pathname-encoding fails on them:

(progn (load "/home/pjb/opt/share/emacs/site-lisp/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.8082" :coding-system "utf-8-unix"))

;; Loading file /home/pjb/.clisprc.lisp ...
:ONE
:TWO
:THREE
*** - SYSTEM::SET-STREAM-EXTERNAL-FORMAT on
#<IO TWO-WAY-STREAM
#<INPUT UNBUFFERED FILE-STREAM CHARACTER #P"/dev/fd/0" @1>
#<OUTPUT UNBUFFERED FILE-STREAM CHARACTER #P"/dev/fd/1">>
is illegal
The following restarts are available:
SKIP :R1 skip (SETF *PATHNAME-ENCODING* # ...)
STOP :R2 stop loading file /home/pjb/rc/clisprc.lisp
C/Break 1 USER[1]>

Of course now I will wrap them in ignore-errors, but perhaps it would be better if SYSTEM::SET-STREAM-EXTERNAL-FORMAT didn't break on these streams?

clisp-2.48 on x86_64, with slime of two days ago.

Discussion

  • Sam Steingold
    Sam Steingold
    2010-06-24

    use an explicit direction argument or wait for a fix in cvs

     
  • Sam Steingold
    Sam Steingold
    2010-06-24

    thank you for your bug report.
    the bug has been fixed in the CVS tree.
    you can either wait for the next release (recommended)
    or check out the current CVS tree (see http://clisp.cons.org\)
    and build CLISP from the sources (be advised that between
    releases the CVS tree is very unstable and may not even build
    on your platform).

     
  • Sam Steingold
    Sam Steingold
    2010-06-24

    • assigned_to: haible --> sds
    • status: open --> closed-fixed