Hello,
I was unsure to which of the lists this belonged best so I posted it to both slime-devel and ecls-list (if I understand, swank which is part of slime handles the implementation-specifics)...
Is slime known to be broken with ECL?
I initially tried with ECL 8.12.0 and first had an unknown utf8-unix external format error (so I adapted my ~/.emacs to temporarily not use utf-8 mode, which helped).
Then there was another error related to missing ext:+ecl-version-number+ constant (which I could declare in ~/.eclrc, which also helped).
However, there then was another error: "Wrong number of arguments passed to function #<compiled-function SI:IHS-TOP>".
I then tried using ECL 9.6.0 (or .1? the ecl-9.6.0 archive had a directory named ecl-9.6.1), built with unicode support. The utf8 related error still occurs when utf8 mode is enabled, the +ecl-version-number+ constant is already defined this time, yet the ihs-top function being called with the wrong number of arguments still occurs.
Backtrace:
LAMBDA swank-backend:call-with-debugger-hook swank:swank-debugger-hook lambda swank-backend:call-with-debugger-hook lambda swank::call-with-bindings swank::call-with-connection swank::simple-serve-requests swank::serve-requests swank::serve-connection swank::serve swank::setup-server swank:start-server si:bytecodes [Evaluation of: (progn (load "/home/mmondor/emacs-scripts/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.9787" :coding-system "iso-latin-1-unix"))] si:bytecodes [Evaluation of: (si:top-level)]
My experience with slime and ecl is limited, I used to use it with SBCL only previously. The reason why my initial tries were with ECL 8.12 was because I got it working properly with threads, when the bootstrap ecl_min appears to segfault and its signal handler stuck in an endless loop when I try to build 9.6.0/1 with threading support (it builds fine non-threaded). But this is another matter which I didn't spend time to debug yet. :)
Thanks,
Latest slime (from CVS) works ok with latest ECL (from git),
:You are rigth that utf-8 coding system doesn't work.
2009/6/25 Matthew Mondor mm_lists@pulsar-zone.net:
Hello,
I was unsure to which of the lists this belonged best so I posted it to both slime-devel and ecls-list (if I understand, swank which is part of slime handles the implementation-specifics)...
Is slime known to be broken with ECL?
I initially tried with ECL 8.12.0 and first had an unknown utf8-unix external format error (so I adapted my ~/.emacs to temporarily not use utf-8 mode, which helped).
Then there was another error related to missing ext:+ecl-version-number+ constant (which I could declare in ~/.eclrc, which also helped).
However, there then was another error: "Wrong number of arguments passed to function #<compiled-function SI:IHS-TOP>".
I then tried using ECL 9.6.0 (or .1? the ecl-9.6.0 archive had a directory named ecl-9.6.1), built with unicode support. The utf8 related error still occurs when utf8 mode is enabled, the +ecl-version-number+ constant is already defined this time, yet the ihs-top function being called with the wrong number of arguments still occurs.
Backtrace: > LAMBDA > swank-backend:call-with-debugger-hook > swank:swank-debugger-hook > lambda > swank-backend:call-with-debugger-hook > lambda > swank::call-with-bindings > swank::call-with-connection > swank::simple-serve-requests > swank::serve-requests > swank::serve-connection > swank::serve > swank::setup-server > swank:start-server > si:bytecodes [Evaluation of: (progn (load "/home/mmondor/emacs-scripts/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.9787" :coding-system "iso-latin-1-unix"))] > si:bytecodes [Evaluation of: (si:top-level)]
My experience with slime and ecl is limited, I used to use it with SBCL only previously. The reason why my initial tries were with ECL 8.12 was because I got it working properly with threads, when the bootstrap ecl_min appears to segfault and its signal handler stuck in an endless loop when I try to build 9.6.0/1 with threading support (it builds fine non-threaded). But this is another matter which I didn't spend time to debug yet. :)
Thanks,
Matt
Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
On Thu, 25 Jun 2009 17:55:51 -0400 Matthew Mondor mm_lists@pulsar-zone.net wrote:
Is slime known to be broken with ECL?
With ECL 9.7.1 slime now works, except that the following wich I used with SBCL don't work (ECL was built with unicode support however):
(set-language-environment "UTF-8") (setq slime-net-coding-system 'utf-8-unix)
I also had to add to ~/.swank.lisp:
(setq swank:*globally-redirect-io* t)
Thanks,
Matthew Mondor mm_lists@pulsar-zone.net writes:
On Thu, 25 Jun 2009 17:55:51 -0400 Matthew Mondor mm_lists@pulsar-zone.net wrote:
Is slime known to be broken with ECL?
With ECL 9.7.1 slime now works, except that the following wich I used with SBCL don't work (ECL was built with unicode support however):
(set-language-environment "UTF-8") (setq slime-net-coding-system 'utf-8-unix)
I also had to add to ~/.swank.lisp:
(setq swank:*globally-redirect-io* t)
Please update to HEAD. This issue, and the one with output going to *inferior-lisp* should be fixed in the current CVS version.
-T.
On Tue, 14 Jul 2009 01:17:56 +0200 "Tobias C. Rittweiler" tcr@freebits.de wrote:
Please update to HEAD. This issue, and the one with output going to *inferior-lisp* should be fixed in the current CVS version.
The one I was running was HEAD from a few days (or at most a week ago), but indeed updating again fixed both issues :)
Thank you very much,
-
Marko Kocić -
Matthew Mondor -
Tobias C. Rittweiler