slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] SLIME and Allegro on Windows
by Peter Seibel 04 Apr '05

04 Apr '05

Does anyone know what the deal is with using Allegro on Windows with SLIME? As in, why it doesn't Just Work. (I've seen Bill Clementson's blog entry--that's the approved work around, right?) Is this something that Franz could fix by providing a console app version of alisp.exe (and one that doesn't have whatever multithreading problem build.exe (the console app version of mlisp.exe) has?) -Peter -- Peter Seibel peter(a)gigamonkeys.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 1

[slime-devel] small patch to slime-xref-quit & feature request.
by Eduardo Muñoz 04 Apr '05

04 Apr '05

Using M-. with a generic function presents a buffer selection thingy. Selecting the desired method or defclass opens the desired buffer but then using q to exit the xrefs buffer restores de window configuration so I have to select the buffer manually. Using C-x o to exit the xref buffer leaves it visible but this is something I want to avoid. So I have installed locally the following patch: Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.477 diff -u -r1.477 slime.el --- slime.el 1 Apr 2005 19:58:20 -0000 1.477 +++ slime.el 1 Apr 2005 21:07:24 -0000 @@ -6065,12 +6066,14 @@ (error "No context for finding locations.")) (funcall slime-next-location-function)) -(defun slime-xref-quit () - "Kill the current xref buffer and restore the window configuration." - (interactive) +(defun slime-xref-quit (arg) + "Kill the current xref buffer and restore the window configuration. +If arg is supplied do not restore configuration." + (interactive "P") (let ((config slime-xref-saved-window-configuration)) (slime-xref-cleanup) - (set-window-configuration config))) + (unless arg + (set-window-configuration config)))) (defun slime-xref-cleanup () "Delete overlays created by xref mode and kill the xref buffer." ---------------------------- The feature request is to send more arguments to slime-translate-to-lisp-filename-function and her sister slime-translate-from-lisp-filename-function, say (lisp-implementation-version) and (machine-instance). I am no elisp expert and failed to work out something like this. The idea is to be able to know if the translation is really needed (emacs on windows, lisp on linux) or not (everything on linux). The easy part is to know where emacs is running and the hard one (that I leave to fine slime hackers :) is to know the lisp host environment. Greetings, -- Eduardo Muñoz | (prog () 10 (print "Hello world!") http://213.97.131.125/ | 20 (go 10))

3 4

[slime-devel] GCL and slime
by Pekka NIiranen 03 Apr '05

03 Apr '05

Hi, why is GCL (http://savannah.gnu.org/projects/gcl/) not supported? -pekka-

3 2

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 01 Apr '05

01 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.651 slime/ChangeLog:1.657 --- slime/ChangeLog:1.651 Sun Mar 27 21:42:54 2005 +++ slime/ChangeLog Fri Apr 1 23:57:42 2005 @@ -1,3 +1,57 @@ +2005-04-01 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-get-buffer): Initialize the buffer local + variables slime-buffer-connection and slime-current-thread when + creating a fresh buffer. + + * swank.lisp (spawn-repl-thread): Use + *default-worker-thread-bindings* just like spawn-worker-thread. + (wrap-sldb-vars): New function. Rebind *sldb-level* to avoid + confusion with recursive errors during eval-in-frame. + (eval-string-in-frame, pprint-eval-string-in-frame): Use it. + + * swank-allegro.lisp (eval-in-frame): Allegro's + eval-form-in-context does nothing special with lexical variables + in the frame. Wrap an explicit LET around the form to get similar + behavior as in the other Lisps. + (inspect-for-emacs (structure-object)): Remove structure related + methods. It's already covered by the general case with + allegro-inspect. + (common-seperated-spec): Deleted + +2005-04-01 Luke Gorrie <luke(a)synap.se> + + * slime.el (slime-xref-mode): Summarise the most important + bindings in the mode description. + + * metering.lisp: Now supports only CLISP and OpenMCL. + Removed a lot of really ugly reader-conditionalized code, much of + it for archaic lisps (#+cltl2, #+lcl3.0, #+mcl1.3.2, etc). + + * swank-source-path-parser.lisp (check-source-path): Signal an + error if a source path is malformed. SBCL sometimes gives (NIL). + (source-path-stream-position): Use it. + + * slime.el (slime-goto-definition): Handle :error locations here + before any window/buffer changes are made. + +2005-04-01 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-keys): Bind slime-edit-definition-other-window + to `C-x 4 .' and slime-edit-definition-other-frame to `C-x 5 .', + shadowing the equivalent find-tag... bindings. + (slime-goto-definition): In the other-window and other-frame cases, + make sure point does not move in the originating window, even when + the definition is found in the same buffer. + +2005-03-31 Luke Gorrie <luke(a)synap.se> + + * doc/slime.texi (slime-selector): New section. + (Inspector): Updated for the post-1.0 inspector. + + * slime.el (slime-selector): Removed unneeded "the" prefixes in + descriptions of what the selector methods do. + 2005-03-27 Helmut Eller <heller(a)common-lisp.net> * PROBLEMS, NEWS, doc/slime.texi: Some updates for the upcoming

1 0

[slime-devel] [Patch] Improve slime-edit-definition-other-window and ...-frame
by Matthias Koeppe 01 Apr '05

01 Apr '05

Hi, I am sending a little patch that improves the commands slime-edit-definition-other-window and ...-frame. Would someone like to merge it into CVS? Cheers, Matthias 2005-03-27 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-keys): Bind slime-edit-definition-other-window to `C-x 4 .' and slime-edit-definition-other-frame to `C-x 5 .', shadowing the equivalent find-tag... bindings. (slime-goto-definition-other-window-aux): New function, adapted from the Emacs function find-tag-other-window. (slime-goto-definition): In the other-window and other-frame cases, make sure point does not move in the originating window, even when the definition is found in the same buffer. --- slime.el.~1.473.~ 2005-03-27 16:35:04.000000000 +0200 +++ slime.el 2005-03-27 17:02:06.000000000 +0200 @@ -555,6 +555,8 @@ ("\C-i" slime-complete-symbol :prefixed t :inferior t) ("\M-i" slime-fuzzy-complete-symbol :prefixed t :inferior t) ("\M-." slime-edit-definition :inferior t :sldb t) + ("\C-x4." slime-edit-definition-other-window :inferior t :sldb t) + ("\C-x5." slime-edit-definition-other-frame :inferior t :sldb t) ("\M-," slime-pop-find-definition-stack :inferior t :sldb t) ("\M-*" slime-pop-find-definition-stack :inferior t :sldb t) ("\C-q" slime-close-parens-at-point :prefixed t :inferior t) @@ -5122,18 +5124,41 @@ (error "No known definition for: %s" name)) (slime-goto-definition name definitions where)))) +(defun slime-goto-definition-other-window-aux (definition) + ;; Taken from the Emacs function `find-tag-other-window': + ;; This hair is to deal with the case where the tag is found in the + ;; selected window's buffer; without the hair, point is moved in both + ;; windows. To prevent this, we save the selected window's point before + ;; doing find-tag-noselect, and restore it after. + (let ((window-point (window-point (selected-window)))) + (slime-goto-source-location (slime-definition.location + definition)) + (let ((tagbuf (current-buffer)) + (tagpoint (point))) + (set-window-point (prog1 + (selected-window) + (switch-to-buffer-other-window tagbuf) + ;; We have to set this new window's point; it + ;; might already have been displaying a + ;; different portion of tagbuf, in which case + ;; switch-to-buffer-other-window doesn't set + ;; the window's point from the buffer. + (set-window-point (selected-window) tagpoint)) + window-point)))) + (defun slime-goto-definition (name definitions &optional where) (slime-push-definition-stack) (cond ((slime-length> definitions 1) (slime-show-definitions name definitions)) (t - (slime-goto-source-location (slime-definition.location - (car definitions))) (cond ((equal where 'window) - (switch-to-buffer-other-window (current-buffer))) + (slime-goto-definition-other-window-aux (car definitions))) ((equal where 'frame) - (switch-to-buffer-other-frame (current-buffer))) + (let ((pop-up-frames t)) + (slime-goto-definition-other-window-aux (car definitions)))) (t + (slime-goto-source-location (slime-definition.location + (car definitions))) (switch-to-buffer (current-buffer))))))) (defun slime-edit-definition-other-window (name) -- Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe

2 6

[slime-devel] Problems with LWW FLI
by Edi Weitz 29 Mar '05

29 Mar '05

Hi! Has anyone else problems with SLIME when using Lispworks on Windows (XP) and its FLI? I've run into a (reproducable but complicated) situation where SLIME simply hung while there were no problems from the LW IDE or from the command line. I'm sitting at my Linux laptop now but I can try to create a simple test case - I just wanted to check if this is a known problem. Cheers, Edi.

4 11

[slime-devel] Class browser: how does it work? [was: Re: [slime-cvs] CVS update: slime/NEWS]
by Paolo Amoroso 29 Mar '05

29 Mar '05

heller(a)common-lisp.net (Helmut Eller) writes: > Modified Files: > NEWS [...] > +* 1.2 (March 2005) [...] > +** M-x slime-browse-classes > +A simple class browser was added. How does it work? I have tried invoking it in a CMUCL SLIME session with McCLIM loaded, passing clim-clx::clx-medium as an argument. I get a buffer containing: Class Browser [+] clim-clx::clx-medium If I hit ENTER on "+", it turns into "X" and nothing else happens. Apparently, any other keystroke displays this error in the echo area: Text is read only: "Attempt to change text outside editable field" I use the latest SLIME and McCLIM CVS sources, CMUCL Snapshot 2005-03 and GNU Emacs 21.3.2 under Slackware Linux 10.0. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

2 3

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 27 Mar '05

27 Mar '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.649 slime/ChangeLog:1.651 --- slime/ChangeLog:1.649 Wed Mar 23 13:23:26 2005 +++ slime/ChangeLog Sun Mar 27 21:42:54 2005 @@ -1,3 +1,13 @@ +2005-03-27 Helmut Eller <heller(a)common-lisp.net> + + * PROBLEMS, NEWS, doc/slime.texi: Some updates for the upcoming + release. + +2005-03-27 Russell McManus <russell_mcmanus(a)yahoo.com> + + * swank-clisp.lisp (getpid): Try sys::process-id if + sys::program-id doesn't exist. + 2005-03-23 Marco Baringer <mb(a)bese.it> * swank.lisp (commit-edited-value): Read a backquated string,

1 0

[slime-devel] small patch for cvs head clisp (backward compatible)
by Russell McManus 27 Mar '05

27 Mar '05

diff -c -r1.45 swank-clisp.lisp *** swank-clisp.lisp 15 Dec 2004 22:35:20 -0000 1.45 --- swank-clisp.lisp 26 Mar 2005 02:15:23 -0000 *************** *** 81,88 **** (funcall fn)) #+unix ! (defmethod getpid () ! (system::program-id)) #+win32 (defmethod getpid () (cond ((find-package :win32) --- 81,90 ---- (funcall fn)) #+unix ! (defmethod getpid () ! (funcall (or (find-symbol "PROGRAM-ID" :system) ! (find-symbol "PROCESS-ID" :system) ! (error "getpid not implemented")))) #+win32 (defmethod getpid () (cond ((find-package :win32) ----------

2 1

[slime-devel] problems with slime CVS and xemacs 21.4.15
by Nathan Froyd 27 Mar '05

27 Mar '05

I think this is really an Emacs problem, but Slime is the first Emacs package I've used where problems like this have come up, so I'm asking here first. I'm running XEmacs 21.4.15 on OS X 10.3.8. I just updated my Slime to the newest, shiniest CVS version (from 1.0 or so), only to find out that it won't work with my XEmacs. Near as I can tell, it's because my XEmacs isn't MULE-ized ({make,find}-coding-system do not exist) and Slime really wants MULE or some semblance thereof to operate. I assume then that Slime does not support non-MULE emacsen...is this a correct assumption? Or do I just need a newer XEmacs that features (some) support for coding systems in non-MULE builds? I see from looking at the archives that people seem to be using Slime CVS in XEmacs, but it's not clear whether those are MULE builds or not. Thanks, -- Nathan | From Man's effeminate slackness it begins. --Paradise Lost

2 1

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