slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Would like to add 'changed definitions' functionality
by Glenn Ehrlich 18 Jun '04

18 Jun '04

Hi, I'd like to add some sort of 'changed definitions' functionality to slime, i.e., be able to to evaluate or compile changed defs in the buffer or all buffers. I'm thinking of modeling this after the changed definitions of Genera (from my new lisp machine :) or LispWorks. I've looked at the similar functionality in ilisp (but you have to manually mark functions) and Franz's eli (which looks like it might be a good starting point). Any particular hints or comments folks would like to make before I start? Any internal functions that might be helpful? -- Glenn Ehrlich http://cooking-with-lisp.blogspot.com

3 4

Re: [slime-devel] SLIME User Survey
by Bill_Clementson＠peoplesoft.com 18 Jun '04

18 Jun '04

> Questions: > > Which Lisp versions do you use SLIME with? Allegro 6.2 and 7.0beta, LispWorks 4.3, CLISP 2.33, and ABCL (cvs) - all on Win2000 > Which Emacs versions? GNU Emacs 21.3.50 > How well does SLIME work for you? Great! I used ILISP and ELI in the past, but SLIME seems to have the best mix of features, stability and portability. I only use SLIME today. > What bugs (reproducible or otherwise) or missing features annoy you? bug: the "v"iew source option in sldb doesn't work for any implementation I'm using feature: it would be *really* nice to have edebug-like debugging in SLIME > Is there some packaging system (e.g. Debian) that you would like to > see SLIME 1.0 bundled with? If so, do you know how to coordinate this? Windows installer - just joking ;-) Debian seems the obvious choice (although I don't use Linux). Kevin Rosenberg has done a fantastic job looking after a lot of the CL packages on Debian (have a look at http://b9.com/debian.html to see a list of the ones he maintains). You might try twisting his arm a little to get him to look after SLIME too :-) > If you said anything negative above then please say something nice > here to make us feel good: SLIME just seems to go from strength to strength - great job you guys! - Bill

1 0

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 18 Jun '04

18 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > Are there any features we can remove? I was going to suggest removing > > the REPL (because the code is messy and a REPL is not the Emacs way to > > interact with anything), but I guess people wouldn't like that :-) > > Amazingly I find myself using the REPL all the time, even though I > never use IELM for Emacs Lisp. I'm not sure why. I also use the REPL all the time and wouldn't like to see it removed. In fact, my normal modus operandi is to jump between source window and REPL, sometimes evaluating sexp's in the source window, sometimes evaluating them in the REPL. Generally, the one-off testing stuff is in the REPL; however, there are often times when I want to step through chunks of code from a source buffer in the REPL and "tweak" the code before it is executed. for that, I use the following function: (defun slime-present () (interactive) (setq *presentation-buffer* (current-buffer)) (global-set-key [f9] (lambda () (interactive) (set-buffer *presentation-buffer*) (forward-sexp) (let ((end (point)) (beg (save-excursion (backward-list 1) (point)))) (copy-region-as-kill-nomark beg end) (set-buffer (slime-output-buffer)) (unless (eq (current-buffer) (window-buffer)) (pop-to-buffer (current-buffer) t)) (goto-char (point-max)) (yank) (slime-reindent-defun) (delete-other-windows))))) This is also useful when I want to give a "slide show" type of presentation of some lisp code or when I want a "clean" REPL session (e.g. -- if I want to post it later to my weblog). So, to reiterate, I LIKE THE REPL. :-) > > Any outstanding keybinding wars? A while ago we talked about grouping > > documentation commands under C-c C-d; I like that idea. > > Agree. We should also move hyperspec-lookup so that `C-c C-h' does the > default action of listing all bindings starting with C-c, and move the > funky-indentation C-M-q command because it's different to the standard > indentation command on that binding (does a whole defun, not sexp at > point). While on the subject of the "grouping" commands, one personal little nitpick that I have is that I don't like the "C-c C-w m" type "grouped" commands. I find that it is easier (and less error prone) for me to type "C-c C-w C-m" instead of "C-c C-w m" because I don't have to lift my finger off the control key to press the m. This was something that we had a number of discussions about among the ILISP developers a while back and the general consensus was in support of the 3-control key sequence. What do others think about this? - Bill

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 18 Jun '04

18 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.397 slime/ChangeLog:1.401 --- slime/ChangeLog:1.397 Wed Jun 16 15:05:27 2004 +++ slime/ChangeLog Thu Jun 17 10:42:39 2004 @@ -1,3 +1,18 @@ +2004-06-17 Luke Gorrie <luke(a)bluetail.com> + + * swank-loader.lisp (binary-pathname): Place fasl files under + ~/.slime/fasl/ instead of the SLIME installation directory. The + installation directory can now be read-only. + (binary-pathname, user-init-file): Removed Win32 + conditionalization. The init file is now called ~/.swank.lisp + instead of ~/_swank.lsp. + + * swank-lispworks.lisp (with-fairly-standard-io-syntax): New + macro. Like with-standard-io-syntax, but keeps the existing values + of *package* and *readtable*. + (dspec-stream-position): Use it. + (quit-lisp): Implemented. + 2004-06-16 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-set-default-directory): Don't call

1 0

[slime-devel] Broken readtables
by Alain.Picard＠memetrics.com 17 Jun '04

17 Jun '04

I have a file which defines a readtable so I can type things like #v(1 2). (Don't ask. :-) When I hit M-. to find any definition in this file, emacs croaks and asks if I want to enter recursive edit. Saying yes yields a SLDB buffer like this: Subcharacter #\v not defined for dispatch char #\#. [Condition of type CONDITIONS:SIMPLE-READER-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [ABORT] Quit process. Now, I grovelled a bit in the sources and found: (defvar *readtable-alist* '() "An alist mapping package names to readtables.") I tried to use this thusly: Try to add what I think is reasonable to this alist CL-USER> (push (cons "GRAPHICS" *readtable*) swank::*readtable-alist*) (("GRAPHICS" . #<READTABLE 202E1B84>)) Verify that it finds the right package CL-USER> (swank::guess-buffer-readtable "graphics") #<READTABLE 202E1B84> Make sure the correct table is in place: CL-USER> (get-dispatch-macro-character #\# #\v (swank::guess-buffer-readtable "graphics")) #<function GRAPHICS::VECTOR-READER 237CF9D2> (looks good). However, the next M-. failed in exactly the same way. Tracing GUESS-BUFFER-READTABLE, I found it was in fact calling it with argument ":graphics", which I thought sub-optimal, but, no matter: CL-USER> (push (cons ":graphics" *readtable*) swank::*readtable-alist*) ((":graphics" . #<READTABLE 202E1B84>) ("GRAPHICS" . #<READTABLE 202E1B84>)) Now, surely it will work, right? Nope. Any clues? Cheers, --ap

5 9

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 17 Jun '04

17 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > > Where should install we SLIME by default? A writable directory would > > be the easiest for us; not sure if distributors like that. > > I hacked swank-loader.lisp to put the fasl files in ~/.slime/fasl/ (on > Win32 it's _slime instead). This way we can install in a read-only > directory. Sound okay? I use Win32 and have plenty of directories in my home directory that start with "dot". There's no reason to make a special exception for Win32 - I would prefer to have the directory name be the same for both Win32 and non-Win32 installs. Another advantage is that, in Emacs, you can elect to not have your dot directories displayed in dired buffers. This is my preference for the fasl directories as I don't normally want to drill down into them. - Bill

4 4

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 17 Jun '04

17 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > I use Win32 and have plenty of directories in my home directory that start > > with "dot". There's no reason to make a special exception for Win32 > > Sounds good to me. But it begs the question: why are we already making > an exception of ~/_swank.lsp vs. ~/.swank.lisp for the init file? > Anyone? Probably because of: 1. Historical Windows/Emacs reasons (older versions of NTEmacs required that the .emacs file be named "_emacs"; however, current versions allow you to use either "_emacs" or ".emacs" as the default initialization file name.) 2, Because some brain-dead Win32 programs won't let you create a file that starts with dot (Windows Explorer is a prime example). However, Emacs on Win32 will let you do this and if you're using slime, you're using Emacs, right? :-) In fact, now even notepad on Win32 will allow you to create files with a dot at the beginning of their name. > Bill, is there some code we can snarf from your blog to make > installation on Win32 easier? We should at least fold your > instructions into the manual. Sure, feel free to grab anything that is useful. I think that most of my slime-related weblog postings are linked to from the "SLIME HOW-TO" page on CLiki (http://www.cliki.net/SLIME-HOWTO). - Bill

1 0

[slime-devel] repl shortcut commands feature request
by Brian Downing 17 Jun '04

17 Jun '04

Continuing my attempts to spam slime-devel: I find the slime-repl comma shortcuts to be quite useful. However, it would be nice if when a comma shortcut was run, if a re-runable version of the command with its arguments could be put in the repl buffer and on the repl command history. That would seem make interacting with the repl a little bit nicer, as it would remove some of the discontinuity between lisp forms (you can see them in the repl buffer, and they can be called up with M-p) and repl commands (you can sometimes see their results in the repl buffer, and they cannot be called up with M-p.) I looked into doing this, but it wasn't immediately obvious to me how I'd accomplish it. (I was going to put the emacs form executed for the shortcut into the buffer prepended by a comma, much like you see the raw emacs forms when you use repeat-complex-command.) -bcd -- *** Brian Downing <bdowning at lavos dot net>

4 6

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 17 Jun '04

17 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.395 slime/ChangeLog:1.397 --- slime/ChangeLog:1.395 Tue Jun 15 17:13:48 2004 +++ slime/ChangeLog Wed Jun 16 15:05:27 2004 @@ -1,3 +1,50 @@ +2004-06-16 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-set-default-directory): Don't call + slime-repl-update-banner in Emacs 20. + (slime-show-source-location, slime-recenter-window): Use + set-window-start instead of recenter; this avoids flickering. + (sldb-list-locals): Don't forget about slime-current-thread in the + temporary buffer. (Fixes bug reported by Mike Beedle.) + (sldb-step): Re-enabled. The CMUCL backend has rudimentary support + for stepping. + + * swank.lisp (*readtable-alist*): Call backend function for + initialization. + (eval-for-emacs, guess-buffer-package): Signal a continuable error + if a package name was supplied but no such package exists. Not + sure if this is better than what we did before (i.e. silently use + the current package). + + * swank-cmucl.lisp (default-directory): Add implementation. + (sldb-step): Uncomment it and remove references to + *swank-debugger-condition*. + + * swank-backend.lisp (sldb-step, default-readtable-alist): New + backend functions. + (emacs-connected): Pass the redirected stream as argument, so that + the OpenMCL backend can add it to CCL::*AUTO-FLUSH-STREAMS*. + + * swank-sbcl.lisp (default-readtable-alist): Implement it. + + * swank-loader.lisp: Move readtable-alist initialization to + swank-sbcl.lisp. + + * swank-allegro.lisp (default-directory, call-with-syntax-hooks): + Add implementations as workarounds for ACL5 bugs. + +2004-06-16 Lawrence Mitchell <wence(a)gmx.li> + + * slime.el (slime-maybe-rearrange-inferior-lisp): Call + `generate-new-buffer-name' manually, rather than relying on the + UNIQUE argument to `rename-buffer' to do so. + +2004-06-16 Frederic Brunel <frederic.brunel(a)in-fusio.com> + + * slime.el (slime-startup-animation): Use defcustom to declare the + variable. + (slime-enable-startup-animation-p): Deleted. + 2004-06-16 Robert Lehr <bozzio(a)the-lehrs.com> * slime.el (slime-backend): This variable can now be set to an

1 0

[slime-devel] Re: Slime?
by Luke Gorrie 16 Jun '04

16 Jun '04

Hi Mike, Sorry about the wait, I put the mail aside while CVS was down. I'm CC'ing the mailing list now that it's back. "Mike Beedle" <beedlem(a)e-architects.com> writes: > Luke: > > Some quick feedback. Overall, SLIME is great. > > I like it much better over ILISP or ELI. > > Here are some comments, mostly on the debugger. (You > may already know some of these things.) > > 1. LINUX > > CMU 18e (Linux) > --------------- > (loaded as inferior lisp) > > 1. s, sldb-step does not work AND causes the connection to > be dropped I've disabled the step command in the Elisp end. It doesn't seem to be implemented by any backend, nor have an interface definition. (Anyone know the history?) > 2. v works on "swank" frames but it does not work for > the compiled code. This works for me. Can you post more details, e.g. a step by step example? The Swank frames aren't treated specially so possibly there is something funky about the other frames your v'ing. > l, d, i, t, r, etc. all work. > > Allegro 6.2 (Linux) > ------------------- > (loaded as inferior lisp) > > 1. s, sldb-step does not work AND causes the connection to > be dropped: > > [Symbol "SLDB-STEP" not found in the SWANK package. > [file position = 28]] (As above.) > 2. v does not work This feature isn't implemented in the ACL backend. > 3. l sort of hangs the process but Ctrl-g get it out of the > state. I don't have ACL installed to test this. Anyone? > 2. XP > > Clisp 2.33.1 (XP) > ----------------- > (loaded as inferior lisp) > > 1. s, sldb-step does not work but there are no sides effects > (as far as I can tell). (As above.) > 2. v, for jumping to the code on the debugger does not work The command isn't implemented in the CLISP backend. > Allegro 6.2 (XP) > ---------------- > (loaded through swank interface through ACL.) > > 1. s, sldb-step does not work AND causes the connection to > be dropped: > > [Symbol "SLDB-STEP" not found in the SWANK package. > [file position = 28]] > > 2. v, for jumping to the code on the debugger does not work These are as above. The last ones sound nasty: > 3. l on the debugger causes both Emacs and Allegro to hang, > but you can get out with Ctrl-g on Emacs and by > hitting RETRUN on Allegro (I think). > 4. Esc (Meta) - . does not work > 5. Get a "broken Allegro process" on exit from Emacs: > > ;; [eof encountered on stream > #<MULTIVALENT stream socket connected from localhost/4005 to > localhost/3809 @ #x206738f2>] Anyone able to investigate? I'm not wild about ACL's licensing mechanism and would prefer not to install it on my computer. Cheers, Luke

2 2

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