slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] (un)trace-package
by William Bland 10 Nov '06

10 Nov '06

I've found this feature quite useful in the couple of days since I implemented it. Thought it might be worth posting it to the list in case it's useful for others too. The feature adds slime commands (un)trace-package, with menu entries under "Debugging". These commands (un)trace all fbound symbols in the named package, which defaults to (slime-current-package). Attached is a diff against current cvs slime. It works for me with a recent cvs emacs and sbcl. Cheers, Bill. -- William Bland: http://www.abstractnonsense.org/ Lisp documentation: http://www.lispdoc.com/

1 0

[slime-devel] Redirecting output from slime-compile-and-load-file?
by Matt Pillsbury 09 Nov '06

09 Nov '06

Hi, I was wondering if it is possible, using SBCL and SLIME, to have the output (errors, warnings, et c.) from slime-compile-and-load-file directed somewhere other than the REPL? The *compilation notes* buffer seems to contain all the information I need, and it's sort of a pain to have those several screenfuls of output dumped to the REPL. I looked around for something like "slime- compile-file-hook", but if it's there I missed it. Many thanks, Matt

3 2

[slime-devel] *source-directory* not defined
by Aycan iRiCAN 08 Nov '06

08 Nov '06

Oneliner aycan.irican@node2 ~/Projects/slime $ cvs diff cvs diff: Diffing . Index: swank-loader.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-loader.lisp,v retrieving revision 1.62 diff -r1.62 swank-loader.lisp 31,32c31,33 < (make-pathname :name nil :type nil < :defaults (or *load-pathname* *default-pathname-defaults*)) --- > (or (asdf::component-pathname (asdf::find-system :swank)) > (make-pathname :name nil :type nil > :defaults (or *load-pathname* > *default-pathname-defaults*))) cvs diff: Diffing doc Best Regards, -- Aycan iRiCAN C0R3 Computer Security Group http://people.core.gen.tr/~aycan.irican/

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 07 Nov '06

07 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.999 slime/ChangeLog:1.1000 --- slime/ChangeLog:1.999 Sun Nov 5 06:35:01 2006 +++ slime/ChangeLog Tue Nov 7 02:42:51 2006 @@ -1,3 +1,8 @@ +2006-11-07 Edi Weitz <edi(a)agharta.de> + + * slime.el (slime-fuzzy-completion-time-limit-in-msec): Escaped + left parenthesis in doc string. + 2006-11-05 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-complete-keywords-contextually): Unused

1 0

[slime-devel] :new-features command
by Brad Beveridge 07 Nov '06

07 Nov '06

Hi all, I'm trying to write a Common Lisp frontend that speaks to a Swank backend. I've just run into a bit of a problem. Let's assume that Swank sends the message (:new-features (:cffi :x86 cffi-features:darwin)). In my code I decode the length of a message then do (with-standard-io-syntax (read-from-string message)) SBCL's reader barfs on the symbol CFFI-FEATURES:DARWIN, because the host side doesn't have have the package CFFI-FEATURES. Which is fair enough. I'm guessing that the Emacs interpreter doesn't bother resolving the symbols, so there is no problem. Later on Slime prefixes ":" in front of the non-keyword symbols, presumably to make them into keyword symbols. Am I understanding this correctly? Is it possible to move the keyword interning to the Swank side? If so, I'll try to write a patch for that. Cheers Brad

5 6

[slime-devel] darcs repo
by Attila Lendvai 07 Nov '06

07 Nov '06

i've invested some time looking into tools keeping repos in sync, chosed this: http://www.darcs.net/DarcsWiki/Tailor for now the darcs repo is at: http://common-lisp.net/project/cl-wdim/darcs/slime/ and will also show up tomorrow at: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi to get it without the extensive patch history (advised, darcsweb is there for looking into the past): darcs get --partial http://common-lisp.net/project/cl-wdim/darcs/slime/ this repo contains all my changes that are missing from cvs head and i'll also try to keep this repo in sync with cvs head, but it would be much better to move it under /project/slime and use darcs. but again, it's up to the dictator who has still not shown up. heh, give me write permission to slime and you won't miss him anymore... :) anyway, the links are there, use them as you like. -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 06 Nov '06

06 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.997 slime/ChangeLog:1.999 --- slime/ChangeLog:1.997 Sat Nov 4 07:02:46 2006 +++ slime/ChangeLog Sun Nov 5 06:35:01 2006 @@ -1,3 +1,12 @@ +2006-11-05 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-complete-keywords-contextually): Unused + variable, removed. + +2006-11-05 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-sexp-highlight-mode): Remove bloat. + 2006-11-04 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> Support nested presentations in REPL results, when present.lisp is

5 7

Re: [slime-devel] Re: slime feature proposal: message-of-the-day
by Jeffrey Cunningham 06 Nov '06

06 Nov '06

Okay. The current manual looks like it was generated with makeinfo. Where can I find the source for that? Is it necessarily desirable to continue using that documentation model? I just put togther documentation for a large set of codes at work using doxygen which, of course, has no Lisp support, but did open my eyes to the possibilities. --Jeff On Sat Nov 04, 2006 at 03:17:12PM +0100, Marco Baringer wrote: > Jeffrey Cunningham <jeffrey(a)cunningham.net> writes: > > > Okay. > > What's the best way to get a comprehensive list of features? > > walk through slime.el and swank.lisp...... > > -- > -Marco > Ring the bells that still can ring. > Forget your perfect offering. > There is a crack in everything. > That's how the light gets in. > -Leonard Cohen >

4 4

[slime-devel] Question about :DEBUG and :DEBUG-ACTIVATE
by Brad Beveridge 06 Nov '06

06 Nov '06

At the protocol level, I don't quite see why :DEBUG and :DEBUG-ACTIVATE do what they do. For a quick recap, Swank sends :DEBUG, and slime calls sldb-setup. Swank then sends :DEBUG-ACTIVATE, for that level of debug, Slime sends back :DEBUGGER-INFO-FOR-EMACS 0 10. When that returns sldb-setup is called again (with the same info it just got?) So it looks to me like there is some redundancy here, could somebody please enlighten me about how :DEBUG and :DEBUG-ACTIVATE work? Cheers Brad

2 2

[slime-devel] single-threaded swank backend and message loops
by Jack Unrue 06 Nov '06

06 Nov '06

I'm trying to understand the behavioral difference that I'm seeing between the sbcl and clisp backends for slime on Windows. First some background. I have Lisp code that enters a loop to process Windows messages. There is a get-message function that blocks until the next message is available, retrieves each such message, and then once that message has been processed, the loop returns to get-message. Eventually, the application exits the message loop and control ultimately returns to the repl. I understand that in single-threaded Lisps like clisp and sbcl/win32, this means that the slime repl will freeze until my message loop exits, though commands that I type ahead will be queued (and that's another nice feature of slime). Now, when I run clisp via slime, this configuration works fine. Messages get processed just fine while in the loop, and slime works just fine between runs of my code (i.e., outside of the message loop). When I run sbcl via slime, not only does the slime repl freeze (which I accept as expected behavior), but the blocking call to get-message never returns either. I can use C-c C-c to interrupt sbcl, though. With some experimental hackery, which I have not yet boiled down to a workable solution, I can actually get a functional message loop running in the slime/sbcl case. This involves bastardizing my code's setup for the loop one time, let that execute and so it immediately returns control to slime, and then restore the correct code. So there seems to be a possibility of achieving the same behavior as I'm getting with clisp. I see that there is a configuration parameter called swank::*communication-style* that I can set in my local .swank.lisp. The swank-sbcl.lisp backend code appears to force the comm style to nil and there is a comment in the preferred-communication-style function about needing to revisit that once sbcl/win32 gets better select() support. I did verify that the comm style is nil when running clisp as well. Does anyone have any thoughts as to what the difference might be between the clisp and sbcl backends in this regard, or possible workarounds to investigate? Thanks in advance. -- Jack Unrue

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel