- slime-devel - mailman3.common-lisp.net

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 29 Aug '07

29 Aug '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1176 slime/ChangeLog:1.1186 --- slime/ChangeLog:1.1176 Mon Aug 27 11:48:58 2007 +++ slime/ChangeLog Tue Aug 28 21:08:39 2007 @@ -1,3 +1,94 @@ +2007-08-28 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + Fix user input type-ahead again (this change from 2007-08-25 got + lost). Testcase: Type (dotimes (i 5) (format t "Number ~A~%" + i) (sleep 1)) and then type ahead while the command is executing + and output arrives. + + * slime.el (slime-repl-insert-prompt): Don't go to point-max but + to slime-repl-input-start-mark if there is one. + (slime-repl-write-string): Insert a :repl-result before the + prompt, not at point-max. Update markers properly. + +2007-08-29 Helmut Eller <heller(a)common-lisp.net> + + * swank-cmucl.lisp (safe-definition-finding): Remove whitespace + around error messages. + (trim-whitespace): New function. + +2007-08-28 Helmut Eller <heller(a)common-lisp.net> + + Fix some output related bugs. + + * swank.lisp (send-repl-results-to-emacs): Emit a fresh line. + + * slime.el (slime-insert-transcript-delimiter): Use + insert-before-markers since slime-output-end is no longer left + inserting. Reported by Austin Haas <austin(a)pettomato.com>. + +2007-08-28 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-display-or-scroll-completions, + slime-scroll-completions): New functions. Factored out of + slime-expand-abbreviations-and-complete. + +2007-08-28 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-repl-write-string): Handle arbitrary targets + using slime-output-target-marker. + (slime-last-output-target-id, slime-output-target-to-marker) + (slime-output-target-marker) + (slime-redirect-trace-output): Move back here from slime-presentations.el. + +2007-08-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (classify-symbol, symbol-classification->string): + Resurrected in swank.lisp. (I was bitten by cvs-pcl which + committed (2007-08-27) my locally changed `contribs/swank-fuzzy.lisp' + where I already removed these functions from.) + +2007-08-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-make-form-spec-from-string): Elisp Hacking 101: + Don't use `beginning-of-buffer' and `end-of-buffer' in Elisp code. + + * swank.lisp (read-form-spec): Unintern just newly interned + symbols when an reader error occurs. + +2007-08-28 Helmut Eller <heller(a)common-lisp.net> + + Move presentations to contrib. Part II. + + * swank.lisp (*listener-eval-function*): New variables. + (listener-eval): Use it + (repl-eval): Used to be listener-eval. + (*send-repl-results-function*): New variable. + (eval-region): Simplify. + (track-package, cat): New functions. + (slime-repl-clear-buffer-hook): New hook. + (slime-repl-clear-buffer): Use it. + +2007-08-28 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + Remove the ID argument from :write-string protocol messages. + Everything, except for rigid-indentation tricks, can be achieved + by using :write-string in conjunction with :presentation-start and + :presentation-end. + + * swank.lisp (present-in-emacs): Unused, removed. + + * swank.lisp (make-output-function-for-target): Remove id argument + from :write-string. + (send-repl-results-to-emacs): Don't call + save-presented-object. Remove id argument from :write-string. + + * slime.el (slime-dispatch-event): Change it here. + (slime-write-string, slime-repl-write-string): And here. + +2007-08-28 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * swank-loader.lisp (*contribs*): Add swank-presentations. + 2007-08-27 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-make-extended-operator-parser/look-ahead): Move

1 0

[slime-devel] Can you afford to lose 300, 000 potential customers per year ?
by Instant＠common-lisp.net 29 Aug '07

29 Aug '07

1 0

[slime-devel] Bug in slime-repl-insert-prompt
by Austin Haas 29 Aug '07

29 Aug '07

The most recent change in CVS: 2007-08-28 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-repl-insert-prompt): Don't go to point-max but to slime-repl-input-start-mark if there is one. This fixes user input type-ahead again (this change from 2007-08-25 got lost). Testcase: Type (dotimes (i 5) (format t "Number ~A~%" i) (sleep 1)) and then type ahead while the command is executing and output arrives. causes the output from one expr in the repl to be placed AFTER the next repl prompt. e.g., CL-USER> (+ 1 2) CL-USER> 3 Desired result: CL-USER> (+ 1 2) 3 CL-USER> -austin

2 1

[slime-devel] repl output behavior
by Austin Haas 28 Aug '07

28 Aug '07

Hi, I just upgraded to the most recent cvs slime this afternoon (previous version was probably about a month old, but I'm not positive), and I noticed that the output in the repl shows up in a different way than I've ever seen. Now, any expression I evaluate (C-x C-e) in a buffer is echoed in the repl in a bottom to top order, starting from above the command prompt. Any output, warnings, etc., appear top to bottom above the echoed expression. Previously, everything flowed from top to bottom with expressions and output intertwined. Was the repl buffer's behavior changed or am I seeing something unintentional? Is there some way to get it back the way that it used to be? -austin

2 3

[slime-devel] OK to move arbitrary :write-string TARGET handler into core?
by Matthias Koeppe 28 Aug '07

28 Aug '07

Helmut, can I move the code to handle arbitrary :write-string TARGETs (via a hashtable of markers) from slime-presentations into core SLIME (see diff)? This code is actually not related to presentations, but is for separating out streams like *trace-output*. Matthias --- slime.el 28 Aug 2007 08:52:04 -0700 1.832 +++ slime.el 28 Aug 2007 09:34:05 -0700 @@ -2970,7 +2970,52 @@ (if (>= (marker-position slime-output-end) (point)) ;; If the output-end marker was moved by our insertion, ;; set it back to the beginning of the REPL result. - (set-marker slime-output-end result-start))))))) + (set-marker slime-output-end result-start))))) + (t + (let* ((marker (slime-output-target-marker target)) + (buffer (and marker (marker-buffer marker)))) + (when buffer + (with-current-buffer buffer + (save-excursion + ;; Insert STRING at MARKER, then move MARKER behind + ;; the insertion. + (goto-char marker) + (insert-before-markers string) + (set-marker marker (point))))))))) + +(defvar slime-last-output-target-id 0 + "The last integer we used as a TARGET id.") + +(defvar slime-output-target-to-marker + (make-hash-table) + "Map from TARGET ids to Emacs markers that indicate where +output should be inserted.") + +(defun slime-output-target-marker (target) + "Return a marker that indicates where output for TARGET should +be inserted." + (case target + ((nil) + (with-current-buffer (slime-output-buffer) + slime-output-end)) + (:repl-result + (with-current-buffer (slime-output-buffer) + slime-repl-input-start-mark)) + (t + (gethash target slime-output-target-to-marker)))) + + +(defun slime-redirect-trace-output () + "Redirect the trace output to a separate Emacs buffer." + (interactive) + (let ((buffer (get-buffer-create "*SLIME Trace Output*"))) + (with-current-buffer buffer + (let ((marker (copy-marker (buffer-size))) + (target (incf slime-last-output-target-id))) + (puthash target marker slime-output-target-to-marker) + (slime-eval `(swank:redirect-trace-output ,target)))) + (pop-to-buffer buffer))) + (defun slime-switch-to-output-buffer (&optional connection) "Select the output buffer, preferably in a different window." -- Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe (currently @math.ucdavis.edu)

2 1

[slime-devel] OK to simplify :write-string message incompatibly?
by Matthias Koeppe 28 Aug '07

28 Aug '07

Helmut, I would like to simplify the :write-string message from (:write-string output &optional id target) to (:write-string output &optional target). (The reason is that ID is not used in core SLIME anymore; and I also do not need it for supporting presentations.) OK to change, or do we need to care about compatibility of the SLIME protocol at this point? Matthias -- Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe (currently @math.ucdavis.edu)

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 28 Aug '07

28 Aug '07

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1171 slime/ChangeLog:1.1176 --- slime/ChangeLog:1.1171 Sun Aug 26 19:36:43 2007 +++ slime/ChangeLog Mon Aug 27 11:48:58 2007 @@ -1,3 +1,47 @@ +2007-08-27 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-make-extended-operator-parser/look-ahead): Move + to end of symbol at point. + (slime-make-form-spec-from-string): Fixes unexpected behaviour of + `save-excursion'. + +2007-08-27 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-sexp-at-point): Fixes a few edge cases were + Emacs' `(thing-at-point 'sexp)' behaves suboptimally. For example, + `foo(bar baz)' where point is at the ?\(. + (slime-internal-scratch-buffer): New. This variable holds an + internal scratch buffer that can be reused instead of having to + create a new temporary buffer again and again. + (slime-make-extended-operator-parser/look-ahead): Uses + `slime-make-form-spec-from-string' to parse nested expressions + properly. + (slime-nesting-until-point): Added docstring. + (slime-make-form-spec-from-string): Added new optional parameter + for stripping the operator off the passed string representation of + a form. Necessary to work in the context of + `slime-make-extended-operator-parser/look-ahead'. Added safety check + against a possible endless recursion. + + * swank.lisp (parse-form-spec): Looses restriction for nesting. + +2007-08-27 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-eval-feature-conditional): Fix typo. + (slime-keywordify): Simplify. + +2007-08-27 Helmut Eller <heller(a)common-lisp.net> + + Move presentations to contrib. Part I. + + * slime.el (slime-event-hooks, slime-dispatch-event): New hook. + (slime-write-string-function, slime-write-string): New hook. + (slime-repl-return-hooks, slime-repl-return): New hook. + (slime-repl-current-input-hooks, slime-repl-current-input): New hook. + (slime-open-stream-hooks, slime-open-stream-to-lisp): New hook. + (sldb-insert-locals, slime-inspector-insert-ispec) + (slime-last-expression): Don't use presentations. + 2007-08-26 Tobias C. Rittweiler <tcr(a)freebits.de> Reduces needless interning of symbols that was introduced by my

1 0

[slime-devel] SWANK and *read-eval*
by Tobias C. Rittweiler 28 Aug '07

28 Aug '07

Hi, *read-eval* is currently set to T everywhere something is READ. While I don't currently see anything that could be (at least easily) exploitable, it still leaves an uneasy feeling in my stomach. Especially in the present of things like autodoc. Therefore I propose the following: (i) Setting *READ-EVAL* to NIL in CALL-WITH-BUFFER-SYNTAX. (ii) Introducing a new macro WITH-SAVE-IO-SYNTAX that expands to (WITH-STANDARD-IO-SYNTAX (LET ((*READ-EVAL* NIL)) ...)) and replacing all occurences of WITH-STANDARD-IO-SYNTAX with this new macro. Any thoughts on this issue? -T.

3 8

[slime-devel] slime-ppcre
by Kilian Sprotte 27 Aug '07

27 Aug '07

Hi, I would like to show you my code that I wrote for grepping through lisp code and for replacing stuff using cl-ppcre. Personally, I find this quite useful - I am curious of course, what you think. You find some informations here: http://www.cliki.net/SLIME-PPCRE There is one thing to note for getting this to load: I had to change swank-loader.lisp: (defvar *contribs* '(swank-fuzzy swank-ppcre) "List of names for contrib modules.") I was doing this on OSX, so I hope it works at least over here... :) Cheers, Kilian

2 1

[slime-devel] [patch] a way to specify custom Emacs indentation right in the Lisp source
by Michael Livshin 27 Aug '07

27 Aug '07

hi all, I find that sometimes the usual Slime way of determining macro indentation based on the position of the &BODY parameter in the argument list is not quite enough. for example: if the body of a certain macro is really a list of function bindings, then one would like those bindings to be indented properly. as it happens, Emacs (or rather common-lisp-indent-function) can be told exactly how to do that, but this information cannot be expressed by the macro argument list alone. the attached patch adds a way to define and access custom indentation specifications like this: <example> (defmacro my-macro (name (&rest args) &body function-bindings) ...) #+swank (setf (swank:emacs-indentation 'my-macro) '(6 4 (&whole 2 &rest (&whole 1 &lambda &body)))) </example> [ which won't work exactly as written, of course, because unfortunately Swank does not push anything onto *FEATURES*... ] thanks, --m * swank.lisp (*emacs-indentation*): New hash table, used to hold custom indentation specs. (emacs-indentation): Accessor for the above. (symbol-indentation): Use it. * slime.el (slime-clean-indent-spec): New function, removes CL package prefixes from symbols sent from Lisp. (slime-handle-indentation-update): Use it.

6 11