slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] [Patch] Fix for out-of-range error when macroexpanding in-place
by Tobias C. Rittweiler 26 May '06

26 May '06

2006-06-26 Tobias C. Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-eval-macroexpand-inplace): Fix out-of-range error on in-place macroexpand when point is placed at a closing parenthesis. In this case the sexp closed by that paren is expanded. Also make expanding of expressions work that are quoted like, for instance, "'(FOO BAR)" if point is placed at the opening paren. --- slime.el-old 2006-05-26 19:44:07.000000000 +0200 +++ slime.el 2006-05-26 21:42:31.000000000 +0200 @@ -7378,10 +7378,17 @@ NB: Does not affect *slime-eval-macroexpand-expression*" (interactive) (lexical-let* ((string (slime-sexp-at-point-or-error)) + (bounds (bounds-of-thing-at-point 'sexp)) + (start (car bounds)) + (end (cdr bounds)) + (point (point)) (package (slime-current-package)) - (start (point)) - (end (+ start (length string))) (buffer (current-buffer))) + ;; SLIME-SEXP-AT-POINT returns "'(FOO BAR BAZ)" even when point is + ;; placed at the opening parenthesis, which wouldn't get expanded + ;; even though FOO was a macro. Hence this workaround: + (when (and (eq ?\' (elt string 0)) (eq ?\( (elt string 1))) + (setf string (substring string 1)) (incf start) (slime-eval-async `(,expander ,string) (lambda (expansion) @@ -7393,7 +7400,8 @@ (delete-region start end) (insert expansion) (goto-char start) - (indent-sexp))))))) + (indent-sexp) + (goto-char point))))))) (defun slime-macroexpand-1 (&optional repeatedly) "Display the macro expansion of the form at point. The form is

1 1

[slime-devel] slime-edit-definition problem
by Gábor Melis 25 May '06

25 May '06

I am running debian/etch with emacs21.4a-3. Some time ago - maybe when emacs was upgraded - M-. stopped working. Well, it works if there are multiple choices, but if there is just one, then it prints the error: Args out of range: #^[t nil 0 1 2 3 4 5 6 7 ... ], -134217682 It seems that find-file-noselect is the culprit, but I have no idea what's wrong with it. The strange thing is that if I define another mapping for slime-edit-definition then that works where the other doesn't: (define-key slime-repl-mode-map "\C-ci" 'slime-edit-definition) It's the same under both sbcl and allegro. Cheers, Gábor

2 3

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

24 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.896 slime/ChangeLog:1.898 --- slime/ChangeLog:1.896 Tue May 16 14:04:49 2006 +++ slime/ChangeLog Wed May 24 23:15:20 2006 @@ -1,3 +1,17 @@ +2006-05-24 Brian Downing <bdowning(a)lavos.net> + + * swank.lisp (recursively-compute-most-completions & friends): + Micro-optimize the fuzzy completion engine, improving performace + by a factor of about 4 on SBCL. However, it will only work on + simple-strings now, and CHAR= is burned in instead of being an + option. I don't think this is too much of a limitation. At this + point rendering the results on the emacs side takes much longer + than finding them for long result lists. + +2006-05-24 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Add some more mop functions to you can inspect classes, + generic functions, methods, slots. + 2006-05-16 Marco Baringer <mb(a)bese.it> * slime.el (slime-repl-return-behaviour): New variable which

1 0

[slime-devel] slime-fuzzy-complete-symbol
by Levente Mészáros 24 May '06

24 May '06

Hi, I'm wondering how others use slime-fuzzy-complete-symbol? Do you use it at all? Do you use it with the default user interface or do you have customized it? I think it's great but the user interface could be tuned a little bit. (at least to my taste) Here is my idea (which I might eventually implement): - in the source window use <TAB> key to show the fuzzy completion list - simultanously in the match window display the possible matches and highlight the first one as being the current fuzzy completion - do not change anything in the source window and let the focus stay there (this is different from the one currently implemented) - use the subsequent <TAB> keypresses to iterate through the possible matches and use S-<TAB> to go backwards. one can always switch to the completion list window and navigate back and forth with the usual keystrokes if one wants to - otherwise the focus stays in the source window and no changes there - if you hit any key that clearly stops editing the current symbol in the source window, then the incomplete symbol will be replaced by the current fuzzy match and the key will be evaluated afterwards (implicit completion). such keys are space, enter, (), arrow keys leaving the symbol, etc... of course, hide completion window - if you did not find a match or there are too many matches, you can continue editing by navigating back, deleting back, etc. - the completion window remains there and continuously updates making the first match as the current completion, so that you can hit space, enter, () to commit to type in slot-value-using-class one would type: ( svuc TAB SPACE object SPACE slot ) levy -- There's no perfectoin

3 6

[slime-devel] REPL-specific printer control variables
by Robert J. Macomber 24 May '06

24 May '06

This patch adds two variables to swank: *listener-print-level* and *listener-print-length*, analogous to the standard Lisp variables *print-level* and *print-length*, used to control how much of a form's return values get printed at the REPL but not of things printed directly by user code. If they're bound (by default, they aren't) then swank uses them when preparing the presentation of an evaluation's result for sending to Emacs. When they're unbound, the values of the standard CL depth and length variables instead. I've written this because of one too many "oops, I forgot to wrap that form in a (progn ... nil)" mistakes on my part. Not a fatal error, but it can be inconvenient. -- Robert Macomber slime(a)rojoma.com

2 3

[slime-devel] significance of *error-output*/*standard-output* in the REPL
by David A Thompson 19 May '06

19 May '06

I suspect this question/issue is already addressed in SLIME documentation (where?) or has been touched on in a mailing list before but... Google and a search of the archives via gmane have let me down so... apologies up front. In short, how does one suppress compiler error warnings in the SLIME REPL (I'm using SLIME with SBCL)? This issue arose in the context of a program which generates thousands of compiler error conditions (intentionally) as it evaluates a large collection of sexps. (As one might imagine), execution is slowed down substantially by the verbosity that accompanies these error messages when each message much be sent to the terminal. Even with a handler in place, SBCL still likes to let everyone know a compiler error has occurred so I end up with thousands of lines in the REPL along the lines of: ; in: LAMBDA NIL ; ((KNOT) ((D1))) ; ; caught ERROR: ; illegal function call Setting *error-output* or *standard-output* to (make-broadcast-stream) is the minimal-effort fix under SBCL if it is used in a regular terminal (e.g., xterm) but, in the context of SLIME, these settings seem to be ignored. SLIME seems to globally redirect streams to the REPL (as the SLIME manual suggests) regardless of *error-output* and/or *standard-output* settings. Is there any way to override this behavior and suppress/divert such error messages? (something related to swank::*globally-redirect-io*?) Thanks for your good graces and any suggestions, - Alan

4 3

[slime-devel] Highlight edits mode
by Levente Mészáros 18 May '06

18 May '06

Is there a way to use highlight edits mode with require? Often I edit several files in several places and then require some system. I would expect resetting highlights in files loaded by require. I know C-c C-c and friends remove highlights but require does not. Probably it's difficult to communicate the loaded files to emacs... How do you use this feature? Cheers, levy -- There's no perfectoin

1 0

[slime-devel] [Patch] improving interaction of macroexpansion and highlighting edits.
by Tobias C. Rittweiler 18 May '06

18 May '06

The attached patch improves the interaction between SLIME-HIGHLIGHT-EDITS-MODE and SLIME-MACROEXPANSION-MINOR-MODE such that macroexpanding in-place will highlight the affected region only. Same happens when going-back to the previous macroexpansion by `undo'. It depends on my last patch which introduces the global variable SLIME-USE-HIGHLIGH-EDITS-MODE. One issue remains: As of now, it's possible to get to an empty Macroexpansion Buffer by `undo'. I have a local hack that all it basically does, is (remap 'undo (lambda (arg) ... (undo arg) (when (zerop (buffer-size)) (redo)))) Though, as you see, that makes use of redo.el which is not part of standard Emacs, unfortunately. 2006-05-18 Tobias C. Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-get-temp-buffer-create): New keyword REUSEP which indicates whether an already-existing buffer named like the buffer to be created should be reused, i.e. not killed, then freshly created. Update docstring accordingly. (slime-with-output-to-temp-buffer): Make &optional arg MODE an &key keyword arg. Add REUSEP keyword. * slime.el (slime-macroexpansion-minor-mode-map): Make remapped `undo' update highlighted edits in the macroexpansion buffer. (slime-eval-macroexpand-in-place): Update highlighted edits when macroexpanding in-place. (slime-eval-macroexpand): Reuse macroexpansion buffer if it exists already to preserve `undo' functionality. --- /home/tcr/src/from-upstream/slime/slime.el 2006-05-18 16:25:50.000000000 +0200 +++ slime.el 2006-05-18 16:34:01.000000000 +0200 @@ -1186,16 +1190,19 @@ "The window config \"fingerprint\" after displaying the buffer.")) ;; Interface -(defun* slime-get-temp-buffer-create (name &key mode noselectp) +(defun* slime-get-temp-buffer-create (name &key mode noselectp reusep) "Return a fresh temporary buffer called NAME in MODE. The buffer also uses the minor-mode `slime-temp-buffer-mode'. Pressing `q' in the buffer will restore the window configuration to the way it is when the buffer was created, i.e. when this function was called. -If NOSELECTP is true then the buffer is shown by `display-buffer', -otherwise it is shown and selected by `pop-to-buffer'." +If NOSELECTP is true, then the buffer is shown by `display-buffer', +otherwise it is shown and selected by `pop-to-buffer'. + +If REUSEP is true and a buffer does already exist with name NAME, +then the buffer will be reused instead of being killed." (let ((window-config (current-window-configuration))) - (when (get-buffer name) (kill-buffer name)) + (when (and (get-buffer name) (not reusep)) (kill-buffer name)) (with-current-buffer (get-buffer-create name) (when mode (funcall mode)) (slime-temp-buffer-mode 1) @@ -1208,14 +1215,17 @@ (current-buffer)))) ;; Interface -(defmacro* slime-with-output-to-temp-buffer ((name &optional mode) +(defmacro* slime-with-output-to-temp-buffer ((name &key mode reusep) package &rest body) "Similar to `with-output-to-temp-buffer'. Also saves the window configuration, and inherits the current `slime-connection' in a buffer-local variable." `(let ((connection (slime-connection)) - (standard-output (slime-get-temp-buffer-create ,name :mode ',mode))) - (prog1 (with-current-buffer standard-output ,@body) + (standard-output (slime-get-temp-buffer-create ,name :mode ',mode + :reusep ,reusep))) + (prog1 (with-current-buffer standard-output + ;; set explicitely to NIL in case the buffer got reused. (REUSEP) + (let ((buffer-read-only nil)) ,@body)) (with-current-buffer standard-output (setq slime-buffer-connection connection) (setq slime-buffer-package ,package) @@ -7018,7 +7028,7 @@ (defun slime-show-apropos (plists string package summary) (if (null plists) (message "No apropos matches for %S" string) - (slime-with-output-to-temp-buffer ("*SLIME Apropos*" apropos-mode) package + (slime-with-output-to-temp-buffer ("*SLIME Apropos*" :mode apropos-mode) package (set-syntax-table lisp-mode-syntax-table) (slime-mode t) (if (boundp 'header-line-format) @@ -7338,6 +7348,8 @@ (remap 'undo '(lambda (&optional arg) (interactive) (let ((buffer-read-only nil)) + (when slime-use-highlight-edits-mode + (slime-remove-edits (point-min) (point-max))) (undo arg))))) (defvar slime-eval-macroexpand-expression nil @@ -7353,8 +7365,10 @@ slime-eval-macroexpand-expression (lambda (expansion) (slime-with-output-to-temp-buffer - ("*SLIME macroexpansion*" lisp-mode) package + ;; reusep for preserving `undo' functionality. + ("*SLIME macroexpansion*" :mode lisp-mode :reusep t) package (slime-macroexpansion-minor-mode) + (erase-buffer) (insert expansion) (font-lock-fontify-buffer)))))) @@ -7373,6 +7387,8 @@ (lambda (expansion) (with-current-buffer buffer (let ((buffer-read-only nil)) + (when slime-use-highlight-edits-mode + (slime-remove-edits (point-min) (point-max))) (goto-char start) (delete-region start end) (insert expansion)

1 0

[slime-devel] [Patch] setting up highlight-edits-mode in a proper way
by Tobias C. Rittweiler 18 May '06

18 May '06

2006-05-18 Tobias Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-use-autodoc-mode): Fix typo in docstring. * slime.el (slime-use-highlight-edits-mode): New variable, analogous to SLIME-USE-AUTODOC-MODE. (slime-setup, slime-lisp-mode-hook): Make above variable work. Also, activates the HIGHLIGHT-EDITS-MODE in proper way (thus avoiding the nasty "Toggling ... off; better pass an explicit argument." message.) * slime.el: Fix typo in comment about communication protocol. --- /home/tcr/src/from-upstream/slime/slime.el 2006-04-15 15:46:14.000000000 +0200 +++ slime.el 2006-05-11 18:09:30.000000000 +0200 @@ -65,7 +65,10 @@ (require 'easymenu) (defvar slime-use-autodoc-mode nil - "When non-nil always enabled slime-autodoc-mode in slime-mode.") + "When non-nil always enable slime-autodoc-mode in slime-mode.") + +(defvar slime-use-highlight-edits-mode nil + "When non-nil always enable slime-highlight-edits-mode in slime-mode") (defun* slime-setup (&key autodoc typeout-frame highlight-edits) "Setup Emacs so that lisp-mode buffers always use SLIME." @@ -73,15 +76,16 @@ (when typeout-frame (add-hook 'slime-connected-hook 'slime-ensure-typeout-frame)) (setq slime-use-autodoc-mode autodoc) - (when highlight-edits - (add-hook 'slime-mode-hook 'slime-highlight-edits-mode))) + (setq slime-use-highlight-edits-mode highlight-edits)) (defun slime-lisp-mode-hook () (slime-mode 1) (set (make-local-variable 'lisp-indent-function) 'common-lisp-indent-function) (when slime-use-autodoc-mode - (slime-autodoc-mode 1))) + (slime-autodoc-mode 1)) + (when slime-use-highlight-edits-mode + (slime-highlight-edits-mode 1))) (eval-and-compile (defvar slime-path @@ -2281,8 +2294,8 @@ This is set only in buffers bound to specific packages.")) ;;; `slime-rex' is the RPC primitive which is used to implement both -;;; `slime-eval' and `slime-eval-async'. You can use it directly you -;;; need to but the others are usually more convenient. +;;; `slime-eval' and `slime-eval-async'. You can use it directly if +;;; you need to, but the others are usually more convenient. (defmacro* slime-rex ((&rest saved-vars) (sexp &optional

1 0

[slime-devel] Search definition
by Levente Mészáros 18 May '06

18 May '06

Hi, I wrote a slime extension to search definitions (variables,.functions, generic functions, etc.) based on fuzzy completions and edit definiton. It's supposed to work like apropos, but the result is interactive. Here is the idea (although not yet fully implemented) + hitting search definitons key brings up minibuffer + while editing in the minibuffer you can press TAB which shows fuzzy competion list for the current content of the minibuffer + completion list has a current selection + up/down arrows move the current selection while leaving the focus in the minibuffer, so that you can edit and hit TAB again to update the completion window + hitting enter goes to the definiton in the source files currently selected and closes minibuffer and completion window and leaves the source buffer open + hitting space opens the definition while leaving the focus in the minibuffer (minibuffer, completion window and definition window is visible at the same time) + hitting space on several definitons will show the sources of the definitons on top of each other + ESC leaves search definition - completion window shows specialized versions of generic functions in place, so that it can be selected directly (tree) - switch between two modes, where changing the selection immediately shows the definition of the current selection, so you can just move up and down (C-SPACE?) - close all sources that were not open before starting find definition except the one that was opened by pressing enter Key bindings are local to search definitions. Any ides, suggestions? levy -- There's no perfectoin

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