slime-devel

slime-devel@common-lisp.net

4231 discussions

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

05 Dec '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1010 slime/ChangeLog:1.1013 --- slime/ChangeLog:1.1010 Mon Dec 4 23:46:06 2006 +++ slime/ChangeLog Tue Dec 5 09:36:34 2006 @@ -1,4 +1,22 @@ +2006-12-05 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (create-swank-server): Removed. Use create-server + instead. + + * slime.el (slime-first-change-hook): Don't do anything if buffers + file doesn't exist. + (slime-start, slime-set-connection-info): Add support for a + :init-function which is called after the usual initialization of the + connection is completed. + + * swank-source-file-cache.lisp (buffer-first-change): Always + return nil and remove the now redundant test with probe-file. + + * swank-backend.lisp (guess-external-format): Return nil if the + file can't be opened. Previusly we wrongly read from stdin. + 2006-12-05 Juho Snellman <jsnell(a)iki.fi> + Real xref support for SBCL (requires SBCL 1.0.0.18). * swank-sbcl.lisp (who-calls): New function, fetch xref data from

1 0

[slime-devel] SLIME can not connect to running SBCL
by vedm 05 Dec '06

05 Dec '06

Latest version of SBCL on Debian, latest SLIME on CVS: I have the image running, try slime-connect, and nothing happens. It doesn't matter if SBCL is running under attachtty or not. When I start SBCL with SLIME (with the "slime" Emacs function), then it starts, but the start-up process stops several times and continues only after I press some key - any key. Any clue? -- vedm

3 5

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

04 Dec '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1009 slime/ChangeLog:1.1010 --- slime/ChangeLog:1.1009 Sun Nov 26 13:08:30 2006 +++ slime/ChangeLog Mon Dec 4 23:46:06 2006 @@ -1,3 +1,28 @@ +2006-12-05 Juho Snellman <jsnell(a)iki.fi> + Real xref support for SBCL (requires SBCL 1.0.0.18). + + * swank-sbcl.lisp (who-calls): New function, fetch xref data from + sb-introspect. + (who-binds): Ditto. + (who-sets): Ditto. + (who-references): Ditto. + (who-macroexpands): Ditto. + (defxref): New macro, create the above functions. + (source-location-for-xref-data): New, map from sb-introspect xref + format to the Swank xref format. + (sanitize-xrefs): Map PCL method names to something more readable. + (string-path-snippet): New function, finds a more accurate source + snippet for definition source locations which have both an + :emacs-string and a full source path available. Otherwise the xref + location would point to the toplevel form rather than the exact + form for functions compiled with C-c C-c. + (source-file-position): New function, somewhat like + source-path-file-position but uses the source-file cache, handles + missing form-paths more gracefully. + (make-definition-source-location): Use the above two functions. + (sbcl-with-xref-p): New function, detect whether SBCL has xref support + for backwards compability. + 2006-11-26 Juho Snellman <jsnell(a)iki.fi> * swank-source-file-cache.lisp (buffer-first-change): Check

1 0

[slime-devel] slime-repl-matching-input-regexp
by Ivan Shvedunov 04 Dec '06

04 Dec '06

Hi. I've sent a patch some time ago that made it possible to use paredit in REPL window without breaking history. It changed the behavior of slime-repl-matching-input-regexp so that the text between the start of current REPL input and the caret is used for history search. The patch was applied on 2006-09-01 by Nikodemus Siivola but later reverted due to some problems that it caused (there was a vague reference to complaints on #lisp). Well, now I had to repatch my copy of slime.el... No big problem with that, but I just wonder what were these negative consequences ? Maybe slime-repl-matching-input-regexp behavior should be made customizable?.. Ivan

2 1

[slime-devel] documentation
by Jeffrey Cunningham 30 Nov '06

30 Nov '06

I just committed changes to doc/slime.texi in CVS. These changes complete the addition of all (current) external functions to the functions index. They are linked to their descriptions. Where there are currently no descriptions I have put them in either slime-mode/Commands/Miscellaneous commands or SLDB: the .../Miscellaneous commands until such time as I or someone else can add descriptions and move them into more suitable locations. If I've left any out, or included (probably) some that shouldn't be there, please let me know. I'm still thinking about how one might do key sub-indices. Regards, --Jeff

1 0

[slime-devel] a per-dialect -connected-hook?
by _deepfire＠feelingofgreen.ru 28 Nov '06

28 Nov '06

Would a patch implementing per-slime-dialect slime-dialect-*-connected-hook by hooking a dispatcher onto slime-connected-hook be deemed a good idea? regards, Samium Gromoff

1 0

[slime-devel] Re: [slime-cvs] CVS slime
by Helmut Eller 27 Nov '06

27 Nov '06

* jsnellman [2006-11-26 19:08+0100] writes: > Log Message: > * swank-source-file-cache.lisp (buffer-first-change): Check > whether a file exists before trying load it into the source > cache. [...] > (defimplementation buffer-first-change (filename) > "Load a file into the cache when the user modifies its buffer. > This is a win if the user then saves the file and tries to M-. into it." > - (unless (source-cached-p filename) > - (ignore-errors (source-cache-get filename (file-write-date filename))))) > + (unless (or (source-cached-p filename) > + (not (ignore-errors (probe-file filename)))) > + (ignore-errors > + (source-cache-get filename (file-write-date filename))))) > I don't understand this change. If the file doesn't exist then OPEN will just fail (which is already handled). And even if PROBE-FILE succeeds, OPEN can still fail, e.g. because some other process deleted the file in between. Which problem does the patch solve?

2 1

[slime-devel] `slime-repl-abort-read' bug?
by Taylor R Campbell 27 Nov '06

27 Nov '06

`slim-repl-abort-read' ignores its two arguments and just pops `slime-read-string-threads' and `slime-read-string-tags'. Is the Lisp system really assumed to request and to abort REPL reads in a LIFO manner, or is this a bug? Or is my understanding of the way SLIME's REPL read mode works bogus?

2 3

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

26 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1007 slime/ChangeLog:1.1009 --- slime/ChangeLog:1.1007 Fri Nov 24 18:34:58 2006 +++ slime/ChangeLog Sun Nov 26 13:08:30 2006 @@ -1,3 +1,21 @@ +2006-11-26 Juho Snellman <jsnell(a)iki.fi> + + * swank-source-file-cache.lisp (buffer-first-change): Check + whether a file exists before trying load it into the source cache. + +2006-11-26 Juho Snellman <jsnell(a)iki.fi> + + Restore the way M-n and M-p used to work in the REPL. (cherry-picked + from a patch with other changes, sent by Attila Lendvai). + + * slime.el (slime-repl-previous-input-starting-with-current-input) + (slime-repl-next-input-starting-with-current-input): New functions, + work like the old slime-repl-previous-input / next-input. + (slime-repl-matching-input-regexp): Restore old version. + (slime-repl-mode-map): Bind s-r-p-i-s-w-c-i and s-r-n-i-s-w-c-i + to M-p and M-n respectively. slime-repl-previous-input and + slime-repl-next-input are still accessible with C-up / C-down. + 2006-11-25 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-repl-read-break): Use a :emacs-interrupt message

1 0

[slime-devel] Patch for CLISP with `readtable-case' set to :invert.
by Lars Rune Nøstdal 26 Nov '06

26 Nov '06

Ok, I'm probably the only one using `readtable-case' set to :invert .. but just in case, here is a patch with changes I had to do to get latest Slime and CLISP-2.41 to start Slime. It's tested with SBCL-0.9.18.43 also: cvs diff: Diffing . Index: metering.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/metering.lisp,v retrieving revision 1.4 diff -u -r1.4 metering.lisp --- metering.lisp 1 Apr 2005 20:16:35 -0000 1.4 +++ metering.lisp 26 Nov 2006 17:13:54 -0000 @@ -359,17 +359,17 @@ ;;; For CLtL2 compatible lisps -(defpackage "MONITOR" (:nicknames "MON") (:use "COMMON-LISP") - (:export "*MONITORED-FUNCTIONS*" - "MONITOR" "MONITOR-ALL" "UNMONITOR" "MONITOR-FORM" - "WITH-MONITORING" - "RESET-MONITORING-INFO" "RESET-ALL-MONITORING" - "MONITORED" - "REPORT-MONITORING" - "DISPLAY-MONITORING-RESULTS" - "MONITORING-ENCAPSULATE" "MONITORING-UNENCAPSULATE" - "REPORT")) -(in-package "MONITOR") +(defpackage :monitor (:nicknames :mon) (:use :cl) + (:export :*monitored-functions* + :monitor :monitor-all :unmonitor :monitor-form + :with-monitoring + :reset-monitoring-info :reset-all-monitoring + :monitored + :report-monitoring + :display-monitoring-results + :monitoring-encapsulate :monitoring-unencapsulate + :report)) +(in-package :monitor) ;;; Warn user if they're loading the source instead of compiling it first. (eval-when (eval) @@ -594,16 +594,16 @@ ;;; ******************************** ;;; Global Variables *************** ;;; ******************************** -(defvar *MONITOR-TIME-OVERHEAD* nil +(defvar *monitor-time-overhead* nil "The amount of time an empty monitored function costs.") -(defvar *MONITOR-CONS-OVERHEAD* nil +(defvar *monitor-cons-overhead* nil "The amount of cons an empty monitored function costs.") -(defvar *TOTAL-TIME* 0 +(defvar *total-time* 0 "Total amount of time monitored so far.") -(defvar *TOTAL-CONS* 0 +(defvar *total-cons* 0 "Total amount of consing monitored so far.") -(defvar *TOTAL-CALLS* 0 +(defvar *total-calls* 0 "Total number of calls monitored so far.") (proclaim '(type time-type *total-time*)) (proclaim '(type consing-type *total-cons*)) @@ -614,7 +614,7 @@ ;;; ******************************** ;;; Perhaps the SYMBOLP should be FBOUNDP? I.e., what about variables ;;; containing closures. -(defmacro PLACE-FUNCTION (function-place) +(defmacro place-function (function-place) "Return the function found at FUNCTION-PLACE. Evals FUNCTION-PLACE if it isn't a symbol, to allow monitoring of closures located in variables/arrays/structures." @@ -628,7 +628,7 @@ (symbol-function ,function-place) (eval ,function-place)))) -(defsetf PLACE-FUNCTION (function-place) (function) +(defsetf place-function (function-place) (function) "Set the function in FUNCTION-PLACE to FUNCTION." (if (fboundp 'fdefinition) ;; If we're conforming to CLtL2, use fdefinition here. @@ -656,7 +656,7 @@ (eval '(setf ,function-place ',function)))) |# -(defun PLACE-FBOUNDP (function-place) +(defun place-fboundp (function-place) "Test to see if FUNCTION-PLACE is a function." ;; probably should be #|(or (and (symbolp function-place)(fboundp function-place)) @@ -665,7 +665,7 @@ (fboundp function-place) (functionp (place-function function-place)))) -(defun PLACE-MACROP (function-place) +(defun place-macrop (function-place) "Test to see if FUNCTION-PLACE is a macro." (when (symbolp function-place) (macro-function function-place))) @@ -705,7 +705,7 @@ (defsetf get-monitor-info (name) (info) `(setf (gethash ,name *monitor*) ,info)) -(defun MONITORED (function-place) +(defun monitored (function-place) "Test to see if a FUNCTION-PLACE is monitored." (and (place-fboundp function-place) ; this line necessary? (get-monitor-info function-place))) @@ -933,7 +933,7 @@ ;;; ******************************** ;;; Main Monitoring Functions ****** ;;; ******************************** -(defmacro MONITOR (&rest names) +(defmacro monitor (&rest names) "Monitor the named functions. As in TRACE, the names are not evaluated. If a function is already monitored, then unmonitor and remonitor (useful to notice function redefinition). If a name is undefined, give a warning @@ -943,13 +943,13 @@ ,@(mapcar #'(lambda (name) `(monitoring-encapsulate ',name)) names) *monitored-functions*)) -(defmacro UNMONITOR (&rest names) +(defmacro unmonitor (&rest names) "Remove the monitoring on the named functions. Names defaults to the list of all currently monitored functions." `(dolist (name ,(if names `',names '*monitored-functions*) (values)) (monitoring-unencapsulate name))) -(defun MONITOR-ALL (&optional (package *package*)) +(defun monitor-all (&optional (package *package*)) "Monitor all functions in the specified package." (let ((package (if (packagep package) package @@ -958,7 +958,7 @@ (when (eq (symbol-package symbol) package) (monitoring-encapsulate symbol))))) -(defmacro MONITOR-FORM (form +(defmacro monitor-form (form &optional (nested :exclusive) (threshold 0.01) (key :percent-time)) "Monitor the execution of all functions in the current package @@ -973,7 +973,7 @@ (report-monitoring :all ,nested ,threshold ,key :ignore-no-calls))) (unmonitor))) -(defmacro WITH-MONITORING ((&rest functions) +(defmacro with-monitoring ((&rest functions) (&optional (nested :exclusive) (threshold 0.01) (key :percent-time)) @@ -995,12 +995,12 @@ "Number of iterations over which the timing overhead is averaged.") ;;; Perhaps this should return something to frustrate clever compilers. -(defun STUB-FUNCTION (x) +(defun stub-function (x) (declare (ignore x)) nil) (proclaim '(notinline stub-function)) -(defun SET-MONITOR-OVERHEAD () +(defun set-monitor-overhead () "Determines the average overhead of monitoring by monitoring the execution of an empty function many times." (setq *monitor-time-overhead* 0 cvs diff: Diffing doc -- Lars Rune Nøstdal http://lars.nostdal.org/

1 0

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