Hi,
I get this error when trying to get a definition of a function:
cond: Error: not finished with #<EXCL.SCM::SOURCE-PART NEW-OFFER-NOTIFICATION :TYPE 133691 133494>
Is it slime or Allegro?
Best, /S
How are you invoking xref through Slime? As a data point I'm using Allegro 8.2 64 and have never seen this error.
Andrew
On Tue, Sep 6, 2011 at 4:37 AM, Slawek Zak slawek.zak@gmail.com wrote:
Hi,
I get this error when trying to get a definition of a function:
cond: Error: not finished with #<EXCL.SCM::SOURCE-PART NEW-OFFER-NOTIFICATION :TYPE 133691 133494>
Is it slime or Allegro?
Best, /S
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Yes. Xref through slime - M-.
Best, /S
On Tue, Sep 6, 2011 at 1:36 PM, Andrew Myers asm198@gmail.com wrote:
How are you invoking xref through Slime? As a data point I'm using Allegro 8.2 64 and have never seen this error.
Andrew
On Tue, Sep 6, 2011 at 4:37 AM, Slawek Zak slawek.zak@gmail.com wrote:
Hi,
I get this error when trying to get a definition of a function:
cond: Error: not finished with #<EXCL.SCM::SOURCE-PART NEW-OFFER-NOTIFICATION :TYPE 133691 133494>
Is it slime or Allegro?
Best, /S
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
In the ACL top level REPL, keywords like ":cd" and ":pwd" have specific meanings. :cd changes the current directory, and :pwd prints it. When I type these into the slime repl, they are just interpreted as keywords. How can I recover the ACL top-level functionality from the slime repl?
Quoth UU UUUUU melbardman@gmail.com:
In the ACL top level REPL, keywords like ":cd" and ":pwd" have specific meanings. :cd changes the current directory, and :pwd prints it. When I type these into the slime repl, they are just interpreted as keywords. How can I recover the ACL top-level functionality from the slime repl?
Type a comma (',') and then type 'cd', 'pwd' e.t.c.
Hit TAB at the prompt for a list of possible commands.
Seb
On Tue, Sep 6, 2011 at 2:57 PM, UU UUUUU melbardman@gmail.com wrote:
Sebastian Tennant <sebyte <at> smolny.plus.com> writes:
Type a comma (',') and then type 'cd', 'pwd' e.t.c.
Hit TAB at the prompt for a list of possible commands.
:cd and :pwd work now, but :cl does not.
C-c C-k slime-compile-and-load-file
C-c C-l slime-load-file
UU UUUUU melbardman@gmail.com writes:
In the ACL top level REPL, keywords like ":cd" and ":pwd" have specific meanings. :cd changes the current directory, and :pwd prints it. When I type these into the slime repl, they are just interpreted as keywords. How can I recover the ACL top-level functionality from the slime repl?
1. It is possible, but not easy (I have some unpublished hack for this purpose, but it takes some time to isolate & publish...).
2. SLIME has its own REPL extensions, activated by , (comma) being the first character, and providing minibuffer prompt, completion and other goodies like that. You might like it even more.
3. There is also a portable REPL in the (quicklispable) gbbopen project. It looks somewhat closer to ACL-REPL, only more complex (it aims at easy extensibility and support for multiple systems/modules). It hooks into SLIME/SWANK automatically (IIRC any load order is ok, either swank-first or gbbopen-first).
In article loom.20110906T192128-799@post.gmane.org, UU UUUUU melbardman@gmail.com wrote:
In the ACL top level REPL, keywords like ":cd" and ":pwd" have specific meanings. :cd changes the current directory, and :pwd prints it. When I type these into the slime repl, they are just interpreted as keywords. How can I recover the ACL top-level functionality from the slime repl?
Don't use Slime's REPL but the native one. You can do that by not using the slime-repl contrib.
T
Tobias C Rittweiler <tcr <at> freebits.de> writes:
In article <loom.20110906T192128-799 <at> post.gmane.org>,
Don't use Slime's REPL but the native one. You can do that by not using the slime-repl contrib.
How does one do that exactly?
I tried commenting out the two "slime-repl" lines in slime-fancy, but when a compile error occurred when I compiled a program, the Lisp listener hung completely. I could not "q" out of the compile buffer window
If someone can post .emacs for a working, version of SLIME (on MacOS and ACL if that matters), that would be helpful.
(I currently have three problems with slime-repl. First, my Lisp listener's startup banner is deleted. Second, I cannot access top-level commands. Third, sometimes I cannot access object presentations properly: sometimes the Lisp listener does not understand a print-unreadable- object's printed representation is a presentation. )
* UU UUUUU [2011-09-14 20:54] writes:
Tobias C Rittweiler <tcr <at> freebits.de> writes:
In article <loom.20110906T192128-799 <at> post.gmane.org>,
Don't use Slime's REPL but the native one. You can do that by not using the slime-repl contrib.
How does one do that exactly?
Allegro's normal REPL is in the *inferior-lisp* buffer.
I tried commenting out the two "slime-repl" lines in slime-fancy, but when a compile error occurred when I compiled a program, the Lisp listener hung completely. I could not "q" out of the compile buffer window
If someone can post .emacs for a working, version of SLIME (on MacOS and ACL if that matters), that would be helpful.
Setup Slime as described in the README file:
(add-to-list 'load-path "~/hacking/lisp/slime/") ; your SLIME directory (setq inferior-lisp-program "/opt/sbcl/bin/sbcl") ; your Lisp system (require 'slime) (slime-setup)
(I currently have three problems with slime-repl. First, my Lisp listener's startup banner is deleted. Second, I cannot access top-level commands. Third, sometimes I cannot access object presentations properly: sometimes the Lisp listener does not understand a print-unreadable- object's printed representation is a presentation. )
Well, you have to choose: either use Allegro's REPL or Slime's REPL. If you load contribs, be prepared for bugs.
Helmut
Helmut Eller <heller <at> common-lisp.net> writes:
- UU UUUUU [2011-09-14 20:54] writes:
Tobias C Rittweiler <tcr <at> freebits.de> writes:
In article <loom.20110906T192128-799 <at> post.gmane.org>,
Don't use Slime's REPL but the native one. You can do that by not using the slime-repl contrib.
How does one do that exactly?
Allegro's normal REPL is in the *inferior-lisp* buffer.
I tried commenting out the two "slime-repl" lines in slime-fancy, but when a compile error occurred when I compiled a program, the Lisp listener hung completely. I could not "q" out of the compile buffer window
If someone can post .emacs for a working, version of SLIME (on MacOS and ACL if that matters), that would be helpful.
Setup Slime as described in the README file:
(add-to-list 'load-path "~/hacking/lisp/slime/") ; your SLIME directory (setq inferior-lisp-program "/opt/sbcl/bin/sbcl") ; your Lisp system (require 'slime) (slime-setup)(I currently have three problems with slime-repl. First, my Lisp listener's startup banner is deleted. Second, I cannot access top-level commands. Third, sometimes I cannot access object presentations properly: sometimes the Lisp listener does not understand a print-unreadable- object's printed representation is a presentation. )
Well, you have to choose: either use Allegro's REPL or Slime's REPL. If you load contribs, be prepared for bugs.
Helmut
I tried using only (slime-setup) as suggested and also using *inferior-lisp*. I still obtain three sets of errors:
1. When slime starts up, in *inferior-lisp* buffer is printed: Warning: These Swank interfaces are unimplemented:
(ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER BACKGROUND-SAVE-IMAGE DUP EXEC-IMAGE FRAME-CALL MAKE-FD-STREAM PROFILE-PACKAGE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SAVE-IMAGE SLDB-BREAK-ON-RETURN SLDB-STEP-INTO SLDB-STEP-NEXT SLDB-STEP-OUT)
2. When I compiled a file that encountered a compilation error, I could not "q" out of the resulting compilation buffer, named *sldb-allegro/1*. Instead, I had to click on "Abort".
3. When I did press "q" in the *sldb-allegro/1* buffer, in the minibuffer was printed the message:
error in process filter: sldb-quit returned [Restart not active [[NIL]]
* UU UUUUU [2011-09-16 01:20] writes:
I tried using only (slime-setup) as suggested and also using *inferior-lisp*. I still obtain three sets of errors:
- When slime starts up, in *inferior-lisp* buffer is printed:
Warning: These Swank interfaces are unimplemented:
(ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER BACKGROUND-SAVE-IMAGE DUP EXEC-IMAGE FRAME-CALL MAKE-FD-STREAM PROFILE-PACKAGE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SAVE-IMAGE SLDB-BREAK-ON-RETURN SLDB-STEP-INTO SLDB-STEP-NEXT SLDB-STEP-OUT)
Those are harmless warnings.
- When I compiled a file that encountered a compilation error,
I could not "q" out of the resulting compilation buffer, named *sldb-allegro/1*. Instead, I had to click on "Abort".
How did you compile the file? With C-c C-k?
- When I did press "q" in the *sldb-allegro/1* buffer,
in the minibuffer was printed the message:
error in process filter: sldb-quit returned [Restart not active [[NIL]]
*sldb-allegro/1* is usually the debugger and q invokes the sldb-quit restart. The error message says that there was no sldb-quit restart. There is no such restart in Allegro's REPL.
Helmut
In article CAEYSiYwOYvxO=25EiMPgzCG9Dbm8Py94SKt8nYm+L=MpZBXRhQ@mail.gmail.com, Slawek Zak slawek.zak@gmail.com wrote:
Hi,
I get this error when trying to get a definition of a function:
cond: Error: not finished with #<EXCL.SCM::SOURCE-PART NEW-OFFER-NOTIFICATION :TYPE 133691 133494>
Is it slime or Allegro?
Best, /S
I don't know. Does that error happen on the Common Lisp side or Emacs side?
You can try to debug it yourself. Look into *slime-events*, try M-x slime-toggle-debug-on-swank-error. There's a function find-definitions or similiar in swank-allegro.lisp.
T
Hi,
I just started teaching Lisp to third year students and of course, they are all trying to install Slime on their laptops.
One has a problem on a MacBook Pro (Lion) that I was unable to solve so far.
He is using slime 2009-09-06 SBCL 1.0.51.0-a546163 GNU Emacs 22.3.1 (i386-apple-darwin9.8.0, Carbon Version 1.6.0)
If anyone has an idea of what the problem is, I would be very grateful for your help.
Irène PS: The *inferior-lisp* buffer looks like that:
(progn (load "/Users/enguerrand-petit/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/var/folders/th/12m02b5s7yqgmbw413kjxfdc0000gn/T/slime.1833" :coding-system "iso-latin-1-unix"))
This is SBCL 1.0.51.0-a546163, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/.
SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/Users/enguerrand-petit/slime/swank-loader.lisp" ; loading #P"/Users/enguerrand-petit/.slime/fasl/2011-08-31/sbcl-1.0.51.0-a546163-darwin-x86/swank-backend.fasl" ; loading #P"/Users/enguerrand-petit/.slime/fasl/2011-08-31/sbcl-1.0.51.0-a546163-darwin-x86/swank-source-path-parser.fasl" ; loading #P"/Users/enguerrand-petit/.slime/fasl/2011-08-31/sbcl-1.0.51.0-a546163-darwin-x86/swank-source-file-cache.fasl"
; compiling file "/Users/enguerrand-petit/slime/swank-sbcl.lisp" (written 01 SEP 2011 11:22:01 AM): ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; compilation aborted after 0:00:00.004 ;; ;; Error while compiling /Users/enguerrand-petit/slime/swank-sbcl.lisp: ;; Don't know how to REQUIRE SB-BSD-SOCKETS. ;; See also: ;; The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS* ;; The SBCL Manual, Function REQUIRE ;; Aborting.
* Irene DURAND [2011-09-08 13:12+0200] writes:
Hi,
I just started teaching Lisp to third year students and of course, they are all trying to install Slime on their laptops.
One has a problem on a MacBook Pro (Lion) that I was unable to solve so far.
[...]
;; Error while compiling /Users/enguerrand-petit/slime/swank-sbcl.lisp: ;; Don't know how to REQUIRE SB-BSD-SOCKETS. ;; See also: ;; The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS* ;; The SBCL Manual, Function REQUIRE ;; Aborting.
The SBCL Manual should contain the necessary info but now after a quick look to www.sbcl.org/manual/ I'm rolling my eyes on The Useless SBCL Manual.
The most likely cause is that SBCL is unable to find the "contrib" directory where SB-BSD-SOCKETS is stored. If I remember correctly, this can be specified with the SBCL_HOME environment variable: SBCL_HOME=<path-where-rest-of-sbcl-is>/contrib.
Anyway, (require 'sb-bsd-sockets) must work before you can compile swank.
Helmut
Helmut Eller heller@common-lisp.net writes:
- Irene DURAND [2011-09-08 13:12+0200] writes:
One has a problem on a MacBook Pro (Lion) that I was unable to solve so far.
[...]
;; Error while compiling /Users/enguerrand-petit/slime/swank-sbcl.lisp: ;; Don't know how to REQUIRE SB-BSD-SOCKETS. ;; See also: ;; The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS* ;; The SBCL Manual, Function REQUIRE ;; Aborting.
The SBCL Manual should contain the necessary info but now after a quick look to www.sbcl.org/manual/ I'm rolling my eyes on The Useless SBCL Manual.
The most likely cause is that SBCL is unable to find the "contrib" directory where SB-BSD-SOCKETS is stored. If I remember correctly, this can be specified with the SBCL_HOME environment variable: SBCL_HOME=<path-where-rest-of-sbcl-is>/contrib.
The other thing that might be wrong, if (require 'sb-bsd-sockets) is failing but (require 'sb-cltl2) does not, is that sbcl executes tests for its contributed modules and refuses to install those modules that don't pass their tests. Given the relative newness of Lion, it's not impossible that something causes the tests for sb-bsd-sockets to fail, which would make (require 'sb-bsd-sockets) give that error. Assuming that sbcl was built and installed without significant customization, that would show up as ls -ld /usr/local/lib/sbcl/sb-bsd-sockets giving an error message.
(if neither Helmut's suggestion nor mine resolves the issue, I think it would be necessary to see more detail about how the user has installed SBCL.)
Cheers,
Christophe
Thanks to you all. In fact, the student found by himself that the problem came from his environment. He has switched to the Lion MacOS distribution and not updated the XCode package.
So now it is working fine. Thanks again for you quick answers.
Irène
Le 09/09/11 19:16, Enguerrand Petit a écrit :
J'ai résolue le problème avec slime, sous l'os Lion il faut le Xcode de l'appstore fait pour lion, j'avais l'ancienne version pour Snow léopard et du coup il manquait un paquet (GNUmake ou makeGNU). Le problème n'était pas slime mais directement sbcl ( et pourtant il marchait) mais il lui manquait ce paquet pour qu'il puisse tourner avec emacs je pense.
Merci pour votre aide,
Enguerrand Petit IN501A3
Le 08/09/11 17:53, Christophe Rhodes a écrit :
Helmut Ellerheller@common-lisp.net writes:
- Irene DURAND [2011-09-08 13:12+0200] writes:
One has a problem on a MacBook Pro (Lion) that I was unable to solve so far.
[...]
;; Error while compiling /Users/enguerrand-petit/slime/swank-sbcl.lisp: ;; Don't know how to REQUIRE SB-BSD-SOCKETS. ;; See also: ;; The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS* ;; The SBCL Manual, Function REQUIRE ;; Aborting.
The SBCL Manual should contain the necessary info but now after a quick look to www.sbcl.org/manual/ I'm rolling my eyes on The Useless SBCL Manual.
The most likely cause is that SBCL is unable to find the "contrib" directory where SB-BSD-SOCKETS is stored. If I remember correctly, this can be specified with the SBCL_HOME environment variable: SBCL_HOME=<path-where-rest-of-sbcl-is>/contrib.
The other thing that might be wrong, if (require 'sb-bsd-sockets) is failing but (require 'sb-cltl2) does not, is that sbcl executes tests for its contributed modules and refuses to install those modules that don't pass their tests. Given the relative newness of Lion, it's not impossible that something causes the tests for sb-bsd-sockets to fail, which would make (require 'sb-bsd-sockets) give that error. Assuming that sbcl was built and installed without significant customization, that would show up as ls -ld /usr/local/lib/sbcl/sb-bsd-sockets giving an error message.
(if neither Helmut's suggestion nor mine resolves the issue, I think it would be necessary to see more detail about how the user has installed SBCL.)
Cheers,
Christophe
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
-
Andrew Myers -
Anton Kovalenko -
Christophe Rhodes -
Helmut Eller -
Irene DURAND -
Irène Durand
-
Liam Healy -
Sebastian Tennant -
Slawek Zak -
Tobias C Rittweiler -
UU UUUUU