slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Did someone say they were working on a GF browser?
by Peter Seibel 31 Jul '04

31 Jul '04

I don't know if I saw it here, on c.l.l., or in my dreams but I seem to recall someone saying they were working on adding a generic function/method browser to SLIME. I.e. something by which you could see all the methods defined on a gf and then remove particular ones easily, etc. If so, how's it coming along? -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

6 15

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 31 Jul '04

31 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.490 slime/ChangeLog:1.492 --- slime/ChangeLog:1.490 Thu Jul 29 20:48:36 2004 +++ slime/ChangeLog Fri Jul 30 14:41:25 2004 @@ -1,3 +1,16 @@ +2004-07-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-connection): Say "No default connection + selected" if there are open connections but no default connection. + (slime-tree-indent-item): Point wasn't updated correctly if the + last line was empty. Use insert-before-markers instead of insert + to do it properly. + (slime-draw-connection-list): Don't break if there is no default + connection. + + * swank-cmucl.lisp (call-with-debugging-environment): Only handle + DI::UNHANDLED-CONDITION not all DI:DEBUG-CONDITIONs. + 2004-07-30 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-choose-overlay-region): Tweaked the

1 0

[slime-devel] Compilation Problem with CVS-Slime
by R. Mattes 30 Jul '04

30 Jul '04

Hello everyone, i just checked out the latest CVS version of Slime, but when i try to load it in emacs (21.3.1) i get the following error: debugger invoked on a SIMPLE-ERROR in thread 17146: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:SPAWN (0)> when called with arguments (# :NAME "Swank"). You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT ] Reduce debugger level (leaving debugger, returning to toplevel). 1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. ((NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:SPAWN (0)> (#<FUNCTION "CLOSURE" {94EE2CD}> :NAME "Swank")) Any idea what's going wrong here? TIA Ralf Mattes

2 1

[slime-devel] no package name on a mode line after 2004-07-19?
by Chisheng Huang 30 Jul '04

30 Jul '04

Slime retrieved from CVS on or before 2004-07-19 would print a package name on the mode line of a buffer editing a Lisp file. After 2004-07-19, Slime stops printing a package name on a mode line. Is this change intentional? It's not documented in the change log. Printing a package name on a mode line is quite useful. Best, -cph

3 3

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 30 Jul '04

30 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.489 slime/ChangeLog:1.490 --- slime/ChangeLog:1.489 Wed Jul 28 14:15:30 2004 +++ slime/ChangeLog Thu Jul 29 20:48:36 2004 @@ -1,3 +1,17 @@ +2004-07-30 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-choose-overlay-region): Tweaked the + multiline-annotation-avoidance code to work with forms not + starting with an open-paren, e.g. `(..) or #'(..). + (slime-update-modeline-package): New configurable. Non-nil (the + default) means update the Lisp package in the modeline using an + idle timer. + (slime-repl-send-input): Make the `slime-repl-old-input' property + cover the whole input (including newline) so that pressing RET on + the end of an input line works. + Use a unique integer as the value of this property to distinguish + adjacent inputs. + 2004-07-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-eval-feature-conditional): Treat uppercase

1 0

[slime-devel] Old REPL input
by Edi Weitz 29 Jul '04

29 Jul '04

I cannot find the old thread but I'm pretty sure this used to work at some point but doesn't work anymore: Start a new SLIME and in the REPL enter and evaluate a simple expression like, say, (+ 3 4) CL-USER> (+ 3 4) 7 CL-USER> Now move point back up until you're behind the closing parentheses and hit the return key. I expected this to move me back to current prompt with "(+ 3 4)" copied there ready to be edited (or evaluated by another return key) but I only get "no input at point." Did I miss a purposeful change or is this is a bug? Thanks, Edi.

4 6

[slime-devel] question on auto-indenting
by rif 29 Jul '04

29 Jul '04

I'm having trouble with auto-indenting in the slime-1.0alpha tarball release. For instance, I have a macro fixfor, which takes an &body argument, and I'd want this to be indented just 2 spaces. It works fine in the REPL, but doesn't seem to work in files at all, whether they use the package that contains the macro or not. Looking at (swank:print-indentation-lossage), I see both fixfor and :fixfor, even though I don't define :fixfor anywhere as far as I know. Furthermore, neither of these are there when I first start CL --- I guess it must add them when it tries to indent the function or something? In any case, fixfor is only defined in a single package, although it's exported from that package, and that package is used by other packages. fixfor is just one example among many, more generally, I don't feel like autoindenting is "working" for me. Possibly relevant facts: swank:*configure-emacs-indentation* is true. In .emacs, my swank:*communiation-style* is :fd-handler. Any help is appreciated. Cheers, rif

2 3

[slime-devel] slime-space ceases to work
by Edi Weitz 29 Jul '04

29 Jul '04

I'm currently working on a mildly complicated web server app using CMUCL 19a-pre3, multi-threading, TBNL, CLSQL, and of course SLIME from CVS. Every now and then slime-space ceases to work, i.e. after I've worked with the system for a while pressing space doesn't produce an arglist in the minibuffer anymore. I've not managed to isolate this problem yet but it occurs rather often and it's really annoying. Is anyone else seeing this? Thanks, Edi.

3 3

[slime-devel] How do I make slime-interactive-eval insert the result in the current buffer?
by Pascal J.Bourguignon 28 Jul '04

28 Jul '04

Hello, I like to have the result of my expressions inserted in the buffer where the expression is. Like with C-u C-x C-e in emacs-lisp-mode. How should I proceed to get this behavior with slime? -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 0

[slime-devel] My personal Slime Feature wishlist
by Thomas Schilling 28 Jul '04

28 Jul '04

I just put together a list of features I'd like to have in SLIME. I think it's better to post it here than letting it get dusty in my home-dir. Consider it as a base of discussion or a possible roadmap for, say, SLIME 2.0 than as a list of must-haves. It's all in the spirit of making SLIME+Lisp the superior tool to accomplish everything :) Of course, I'm willing to contribute, too. They are ordered in terms of (by me) estimated efford. * Nicer Homepage How about this?: http://www.inf.tu-dresden.de/~s3815210/slime-hp-suggestion/ * Class Browser Open a window where the class under the point is shown with all its direct superclasses and its direct subclasses or all of both. - `s' shows/hides the class' direct slots - `m' shows/hides all methods specializing on the class * Source Outline Mode Provide an outline mode for lisp source. That is the user can collapse/expand single lisp expressions. - The keybindings should be the same as in the text outline mode. - What do we show of collapsed expressions? Should a `defun' include the argument list? Should it be specific to the expression being collapsed? Should every expression be collapsible? - A block of comments may be considered a) as a single sexp b) as belonging to the next sexp (if it's on a separate line) or to the provious sexp (if it's on the same line) I favour b) since it would make a full-collapsed file more concise. * Refactoring Aids Provide commands for refactoring operations. Examples for useful Lisp-refactorings are: - extract/inline function/method - move slot to super-/subclass - inline temp/replace temp with query - rename function/class/slot/variable/... - ... - We have to work out which refactorings from [1] are applicable to Lisp (and make sence) and which additional refactorings would be useful for Lisp. - Some refactorings are really hard to implement. Namely all that require a code walker - Note that refactorings are considered save modifications on _working_ code in order to ease implementation of new features. It might still be worth considering how much refactoring is possible without assuming that the code is already compiled and DTRT. * Program Slicing Display (only) all the code that can effect a specified object. For example if invoked on a slot name display all expressions that may change this slot's value _and_ show all expressions that effect these former statements. - How much effort would it take to implement this? - Is it really useful for lisp? (Since lisp does indeed have side-effects, I think it would be of a certain use. So maybe the question should be: How much useful can it be for lisp?) - Can we cover all cases? - What additional information would be needed? Footnotes: [1] "Refactoring - Improving the Design of Existing Code" by Martin Fowler et. al., Addison Wesley, 2000 Regards, -ts -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________

4 9

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