slime-devel November 2006

slime-devel@common-lisp.net

42 participants
58 discussions

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

[slime-devel] Request for committers
by Nikodemus Siivola 05 Nov '06

05 Nov '06

When committing patches from slime-devel, please send a reply to the appropriate threads, saying something like "Just committed, thanks!". ...or at least I would appreciate it greatly: otherwise it can get timeconsuming to vacuum the mailing list for pending patches. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."

1 0

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

05 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.996 slime/ChangeLog:1.997 --- slime/ChangeLog:1.996 Fri Nov 3 12:34:50 2006 +++ slime/ChangeLog Sat Nov 4 07:02:46 2006 @@ -1,3 +1,14 @@ +2006-11-04 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + Support nested presentations in REPL results, when present.lisp is + loaded. + + * swank.lisp (make-presentations-result): New, factored out from + listener-eval. + (listener-eval): Use it here. + + * present.lisp (make-presentations-result): Override it here. + 2006-11-03 Marco Baringer <mb(a)bese.it> * swank.lisp (all-slots-for-inspector): Added declare ignore for @@ -5,16 +16,16 @@ 2006-11-01 Attila Lendvai <attila.lendvai(a)gmail.com> - * slime.el (sldb-sexp-highlight-mode): New custom. - (slime-handle-repl-shortcut): Trigger slime-lookup-shortcut when + * slime.el (sldb-sexp-highlight-mode): New custom. + (slime-handle-repl-shortcut): Trigger slime-lookup-shortcut when the point is anywhere before slime-repl-input-start-mark. IOW, you can press "," anywhere before the prompt. - (slime-edit-definition): Handle the case when there are only such + (slime-edit-definition): Handle the case when there are only such entries returned from swank that have errors. - (slime-read-from-minibuffer): Allow overriding of the keymap. - (slime-repl-previous-matching-input): Similar behaviour like + (slime-read-from-minibuffer): Allow overriding of the keymap. + (slime-repl-previous-matching-input): Similar behaviour like isearch-forward. - (slime-repl-next-matching-input): Ditto. In more details: You can + (slime-repl-next-matching-input): Ditto. In more details: You can freely navigate with slime-repl-previous/next-input with M-p and M-n at any time among the history entries. When M-r is pressed, which invokes slime-repl-previous-matching-input, the the @@ -25,16 +36,16 @@ M-r get the next match, and of course the same applies for M-s, which is slime-repl-previous-matching-input. - * swank.lisp (fuzzy-completion-set): Fix on clisp. - (convert-fuzzy-completion-result): Fix symbol fbound and other + * swank.lisp (fuzzy-completion-set): Fix on clisp. + (convert-fuzzy-completion-result): Fix symbol fbound and other annotations. - (slot-value-using-class-for-inspector): New. - (slot-boundp-using-class-for-inspector): New. - (inspect-for-emacs): Use the special slot access methods so that + (slot-value-using-class-for-inspector): New. + (slot-boundp-using-class-for-inspector): New. + (inspect-for-emacs): Use the special slot access methods so that it's possible to customize the inspecting of complex slots (e.g. computed-class at http://common-lisp.net/project/computed-class/). - (all-slots-for-inspector): Converted to generic method. + (all-slots-for-inspector): Converted to generic method. 2006-11-01 Marco Baringer <mb(a)bese.it>

1 0

[slime-devel] revive M-p in repl navigation due to #lisp requests and other changes
by Attila Lendvai 04 Nov '06

04 Nov '06

this is my current cvs diff of slime (so, this patch makes my previous mails obsolete). 2006-11-04 Attila Lendvai <attila.lendvai(a)gmail.com> * slime.el (slime-repl-kill-input): Also reset the history navigation and when point is right after the prompt then delete the entire repl input. (slime-repl-delete-from-input-history): New. Deletes the current repl input from the history after merging it with the saved version, then overwrite the saved history, so it will not be re-added when normally saving the repl history. Bound to "\M-\C-d" by default. (slime-repl-merge-histories): Use a hashtable for uniqueness check. (sldb-sexp-highlight-mode): Fix for GNU Emacs not having 'paren-mode. (slime-repl-previous-input-starting-with-current-input): Revive old M-p behaviour in the repl due to #lisp demand. Two other ways to navigate the history is M-up to move a single position and M-r to search for a regexp, M-r again to search for the last regexp. Display the current regexp in various minibuffer messages. -- - 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] v-iew source in backtrace not working?
by Jonathon McKitrick 04 Nov '06

04 Nov '06

In the debugger/backtrace, hitting 'v' on a line usually goes to the source code and brackets the form in question in highlighted blocks. Assuming the debug settings were correct during compilation. But I keep getting this now: error in process filter: Symbol's value as variable is void: paren-mode I checked the ChangeLog for paren-mode, and didn't find it. Is this a new setting I forgot to add? I'm running SBCL 0.9.18 on OSX-Intel and CVS Slime, of course. Jonathon McKitrick -- My other computer is your Windows box.

2 2

[slime-devel] slime feature proposal: message-of-the-day
by Marco Baringer 04 Nov '06

04 Nov '06

hi, i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat: we have a new variable swank:*motd-pathname* which, when not NIL, is assumed to name a ChangeLog formated file. When we connect slime to swank this file is read and the entries in the last N days are given to slime to be inserted into the repl before the prompt and after the banner. The idea behind this variable is tha a group of programmers would use it to communicate or remind themselves about development related changes (i'm thinking stuff like changes to default startup procedures, moving databases, api changes, test suite results, etc.). so, would this actually be useful or is it just bloat? (including the ChangeLog parser it's around 80 lines of code). -- -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

7 8

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

04 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.995 slime/ChangeLog:1.996 --- slime/ChangeLog:1.995 Thu Nov 2 06:13:24 2006 +++ slime/ChangeLog Fri Nov 3 12:34:50 2006 @@ -1,3 +1,8 @@ +2006-11-03 Marco Baringer <mb(a)bese.it> + + * swank.lisp (all-slots-for-inspector): Added declare ignore for + unused argument inspector (openmcl warns about this). Reindented. + 2006-11-01 Attila Lendvai <attila.lendvai(a)gmail.com> * slime.el (sldb-sexp-highlight-mode): New custom.

1 0

[slime-devel] sldb-sexp-highlight-mode
by Helmut Eller 04 Nov '06

04 Nov '06

Ahoy, sldb-highlight-sexp is currently broken in Emacs because paren-mode is XEmacs specific. Does somebody care about sldb-sexp-highlight-mode? Otherwise I'm going to delete it and restore the old code. Helmut.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel November 2006