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

[slime-devel] eval compile dwim
by jan 10 Dec '03

10 Dec '03

I don't like jumping back and forth between a buffer and the repl when testing small snippets of code, I prefer to temporarily insert them into the buffer and eval them in place. This creates problems in slime because some features (who-calls, compiler notes) only work properly with compilation, which means I have to use both eval and compile for this strategy to be effective. This leads to errors when done manually so I defined this function: (defun slime-eval/compile-defun-dwim (&optional arg) "Call the computation command you want (Do What I Mean). Look at defun and determine whether to call `slime-eval-defun' or `slime-compile-defun'. A prefix of `-' forces evaluation, any other prefix forces compilation." (interactive "P") (case arg ;; prefix is `-', evaluate defun ('- (slime-eval-defun)) ;; no prefix, automatically determine action ('nil (if (string-match "^(def" (slime-defun-at-point)) (slime-compile-defun) (slime-eval-defun))) ;; prefix is not `-', compile defun (otherwise (slime-compile-defun)))) I use this command all the time so I bind it on M-j. This is bound to indent-new-comment-line by default but it isn't missed since it is also bound on C-M-j. Having the command bound on a Meta key is useful because I don't have to release Meta to M-n or M-p if I get compiler notes. I thought this might be helpful, but maybe I'm missing something. How do other people typically interact with lisp? What are the most commonly used commands? -- jan

3 5

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 08 Dec '03

08 Dec '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.142 slime/ChangeLog:1.145 --- slime/ChangeLog:1.142 Sat Dec 6 16:41:40 2003 +++ slime/ChangeLog Sun Dec 7 20:44:08 2003 @@ -1,3 +1,38 @@ +2003-12-08 Luke Gorrie <luke(a)bluetail.com> + + * swank-cmucl.lisp (*debug-definition-finding*): Now nil by + default, so that errors while looking for definitions are printed + as a message and not debugged. + + * slime.el (slime-read-from-minibuffer): Now the only + completing-read function, stale ones deleted. + +2003-12-07 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (sldb-prune-initial-frames): Use regexp-heuristics and + the '--more--' token to avoid showing the user Swank-internal + backtrace frames initially. + (slime-repl-current-input): Don't include the final newline + character, to make backtraces prettier. + (slime-autodoc): Fixed annoying case where autodocs would be + fetched in a loop for undocumented symbols. + + * swank.lisp (compound-prefix-match): New name and rewritten for + speed. Completion is much faster now. + (*sldb-initial-frames*): Send up to this many (default 20) + backtrace frames to Emacs when entering the debugger. + +2003-12-07 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp, swank-backend.lisp, swank-cmucl.lisp, + swank-lispworks.lisp, swank-openmcl.lisp, swank-sbcl.lisp + (function-source-locations): Make it at generic function. + (function-source-location-for-emacs): Removed. Fixes bug reported + by Marco Baringer. + + * slime.el (slime-interactive-eval): Insert the result at point, + if called with prefix argument. + 2003-12-06 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-easy-menu): Added menubar support, contributed @@ -20,9 +55,9 @@ should be a symbol. (find-function-locations): Return errors as a list of one error. (call-with-debugging-environment): Set *print-level* to 4 and - *print-level* to 10. (Where both nil.) + *print-length* to 10. (Both where nil.) (source-location-for-emacs): Fall back to the location of the - function, if there is no block-debug-info. + function, if there is no debug-block-info. (safe-source-location-for-emacs): Don't catch all conditions; only errors. *compile-filename*: New variable

1 0

[slime-devel] longer initial backtrace
by Luke Gorrie 08 Dec '03

08 Dec '03

Ahoy, I checked in the change we discussed to fetch more backtrace frames by default, and use the '--more--' token to try and avoid shoving our "SWANK"-related frames in your face. I did it with a regexp on the elisp side. One thing to look out for is that SBCL on PPC gets an error trying to format certain backtrace frames, and since this change generally causes more frames to get formatted it can provoke the problem. The only trouble case seen so far is doing "(/ 1 0)" in the REPL. Dan's looking into it. Meanwhile, if it causes you grief you can bung (setq swank::*sldb-initial-frames* 1) into your ~/.swank.lisp to get the old behaviour back. Cheers, Luke

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 07 Dec '03

07 Dec '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.137 slime/ChangeLog:1.142 --- slime/ChangeLog:1.137 Thu Dec 4 16:36:02 2003 +++ slime/ChangeLog Sat Dec 6 16:41:40 2003 @@ -1,3 +1,36 @@ +2003-12-06 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-easy-menu): Added menubar support, contributed + by Friedrich Dominicus. + +2003-12-06 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp: New file. + + * swank-loader.lisp (user-init-file): Translate logical + pathnames. Reported by Friedrich Dominicus. + + * swank-sbcl.lisp (handle-notification-condition): Don't ignore + warnings without context. + (compiler-note-location, brief-compiler-message-for-emacs, + compiler-note-location): Handle null context. + (compile-file-for-emacs): Bind *compile-filename* and load the + fasl file only if it exists. + (function-source-location): The name argument is now optional and + should be a symbol. + (find-function-locations): Return errors as a list of one error. + (call-with-debugging-environment): Set *print-level* to 4 and + *print-level* to 10. (Where both nil.) + (source-location-for-emacs): Fall back to the location of the + function, if there is no block-debug-info. + (safe-source-location-for-emacs): Don't catch all conditions; only + errors. + *compile-filename*: New variable + (open-listener): Don't make the socket non-blocking. + + * slime.el (slime-eval/compile-defun-dwim): New command. + Suggested by "jan" <janmar(a)iprimus.com.au>. + 2003-12-04 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-debugging-state): Don't set sldb-level after

3 2

[slime-devel] [bug] function-source-location-for-emacs
by Marco Baringer 07 Dec '03

07 Dec '03

in swank-backend this function is defined as a generic function, yet every swank-<IMPLEMENTATION> defines it as a regular function. openmcl gives an error while loading slime because of this. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

2 1

[slime-devel] Maybe someone likes menues too
by Friedrich Dominicus 07 Dec '03

07 Dec '03

I know quite a few keystrokes under XEmacs but with every new mode a lot more are suddendly there ;-) Now I can not remember all those keystrokes in any of the modes so I'm sometimes quite happy to have some menu. I did not find one for slime so I wrote one. Feel free to use and comment on it. I assume I will polish it over time, so you can see it as Version 0.1 ;-) It is not really tested and I have just used it under Debian/Linux XEmacs 21.4 somewhat Hope that at least some of you will like it. Regards Friedrich ;;;; Generated header ;;;; $Id$: ;;;; $Log$: ;;;; Author: Friedrich Dominicus ;;;; Created: 2003-12-06 13:47:04 frido ;;;; License: Do whatever you like with it but do not sue me for anything related to it ;;; Initial version for a menu for SLIME ;;; Just a rough try to get something which might be useful ;;;; TODO ;;; This list ought be be quit a bit longer ;-) ;;; - Check all the entries ;;; - see what other commands might be useful ;;; - thinking about a sensible menu for the inferior slime buffer ;;; - a useful context menu (menu are quite a bit away on a large screen ;;; - other things (feel free to add) (require 'easymenu) (require 'slime) (eval-when (load compile eval) (unless (featurep 'hyperspec) (load-library "hyperspec"))) ;;; (setf slime-cl-easy-menu nil) (defvar slime-cl-easy-menu `("Slime" [ "Complete Function" slime-complete-symbol t] [ "Eval Defun" slime-eval-defun t] [ "Eval Last Expression" slime-eval-last-expression t] [ "Eval and Print" slime-pprint-eval-last-expression t ] "--" ("Compilation" [ "Compile Defun" slime-compile-defun t] [ "Compile/Load File" slime-compile-and-load-file t ] [ "Compile File" slime-compile-file t]) "--" ("Compiler Messages" [ "Next" slime-next-note t ] [ "Previous" slime-previous-note t ] [ "Remove Notes" slime-remove-notes t]) "--" ("Definitions" [ "Edit Funtion" slime-edit-function t ] [ "Go back" slime-pop-find-definition-stack t]) ; not a good name reall ; any one with a better name? "--" ("Cross Ref" [ "Who Calls" slime-who-calls t ] [ "Who References " slime-who-references t ] [ "Who Sets" slime-who-sets t ] [ "Who Binds" slime-who-binds t ] [ "Who Macroexpands" slime-who-macroexpands t ] [ "Next Location" slime-next-location t ]) "--" ("Documentation" [ "Describe Symbol" slime-describe-symbol t ] [ "Apropos" slime-apropos t] [ "Hyperspec" hyperspec-lookup t]) )) ;; (slime-lisp-mode-hook-fun) (add-hook 'lisp-mode-hook #'slime-register-menu) (defun slime-register-menu () (interactive) (if (and (featurep 'easymenu) (featurep 'slime)) (progn (easy-menu-define menubar-slime slime-mode-map "Slime" slime-cl-easy-menu) (easy-menu-add slime-cl-easy-menu 'slime-mode-map)) (message "Could not register menu"))) (defun slime-unregister-menu () (interactive) (easy-menu-remove slime-cl-easy-menu)) (provide 'slime-menu) ;;;; Generated header ;;;; $Id$: ;;;; $Log$: ;;;; Author: Friedrich Dominicus ;;;; Created: 2003-12-06 13:47:04 frido ;;;; License: Do whatever you like with it but do not sue me for anything related to it (require 'easymenu) (require 'slime) (require 'cl) ; want to be able to use the common lisp stuff ; not all Emacs do understand even 'unless' ;( ;;; no lisp mode without the hyperspec (eval-when (load compile eval) (unless (featurep 'hyperspec) (load-library "hyperspec"))) ;;; Initial Menu version. A lot of questions still remain ;;; do the categories make sense. The order is arbitrary but should ;;; better reflect hwo often an entry will get used. Long mouse moves ;;; otherwise needed that's not really desirable (defvar slime-cl-easy-menu `("Slime" [ "Complete Function" slime-complete-symbol t] [ "Eval Defun" slime-eval-defun t] [ "Eval Last Expression" slime-eval-last-expression t] [ "Eval and Print" slime-pprint-eval-last-expression t ] "--" ("Compilation" [ "Compile Defun" slime-compile-defun t] [ "Compile/Load File" slime-compile-and-load-file t ] [ "Compile File" slime-compile-file t]) "--" ("Compiler Messages" [ "Next" slime-next-note t ] [ "Previous" slime-previous-note t ] [ "Remove Notes" slime-remove-notes t]) "--" ("Definitions" [ "Edit Funtion" slime-edit-function t ] [ "Go back" slime-pop-find-definition-stack t]) ; not a good name suggestions welcome "--" ("Cross Ref" [ "Who Calls" slime-who-calls t ] [ "Who References " slime-who-references t ] [ "Who Sets" slime-who-sets t ] [ "Who Binds" slime-who-binds t ] [ "Who Macroexpands" slime-who-macroexpands t ] [ "Next Location" slime-next-location t ]) "--" ("Documentation" [ "Describe Symbol" slime-describe-symbol t ] [ "Apropos" slime-apropos t] [ "Hyperspec" hyperspec-lookup t]) )) ;; (slime-lisp-mode-hook-fun) (add-hook 'lisp-mode-hook #'slime-register-menu) (defun slime-register-menu () "Register a menu for SMILE. Initial version probably with typos and definitly not complete. I will improve on it over time." (interactive) (if (and (featurep 'easymenu) (featurep 'slime)) (progn (easy-menu-define menubar-slime slime-mode-map "Slime" slime-cl-easy-menu) (easy-menu-add slime-cl-easy-menu 'slime-mode-map)) (message "Could not register menu for Slime"))) (defun slime-unregister-menu () "Clean up the menu for SMILE. Good guy clean up their stuff themselves ;-)" (interactive) (easy-menu-remove slime-cl-easy-menu)) (provide 'slime-menu)

4 5

[slime-devel] Needed patches for running slime in XEmacs?
by Friedrich Dominicus 06 Dec '03

06 Dec '03

Don't know if this has been posted here before. I'm using XEmacs 21.4 and CMUCL (lisp-implementation-version) "CVS release-18e-branch + minimal debian patches" I don't know if this things are fixed in other version but I had to add the following line to easy-mmode.el (defalias 'define-minor-mode 'easy-mmode-define-minor-mode) and change this in swank-loader.lisp (defun user-init-file () "Return the name of the user init file or nil." (let ((filename (format nil "~A/.swank.lisp" (namestring (truename (user-homedir-pathname)))))) (cond ((probe-file filename) filename) (t nil)))) I tried more than once with CMUCL but it seems as if a dot in a logical pathname is not allowed. Can anyone confirm that? Regards Friedrich

2 1

[slime-devel] Bachelor's Diploma, Master's, or PhD - No Classes Necessary...dirk
by Dustin Chaney 06 Dec '03

06 Dec '03

Academic Qualifications available from prestigious NONACCREDITTED universities. Do you have the knowledge and the experience but lack the qualifications? Are you getting turned down time and time again for the job of your dreams because you just don't have the right letters after your name? Get the prestige that you deserve today! Move ahead in your career today! Bachelors, Masters and PhD's available in your field! No examinations! No classes! No textbooks! Call to register and receive your qualifications within days! 24 hours a day 7 days a week! 203-286-2187 - USA bjsox qnewnlarn nuje tcfd tcpjdpkqgt drhysm qvw sa rur xxagpq

1 0

[slime-devel] Remote-Control Boats & Cars - Great Xmas Gifts.....francisco
by Cory Temple 06 Dec '03

06 Dec '03

1 0

[slime-devel] SLIME on a local socket
by Daniel Barlow 06 Dec '03

06 Dec '03

Hacked up this afternoon, not quite ready for commital but would appreciate feedback: slime on a local (a.k.a unix domain) socket using half of the attachtty/detachtty utility as a socket shim. Why? Two reasons: (1) access control can be done by setting appropriate filesystem permissions on the directory containing the socket (or in Linux but not portably, on the socket itself) - so, a safe way to run slime on shared hosts that doesn't involve cooking up an authentication protocol (2) attachtty can connect across a network using ssh, so you can control a remote lisp this way as well. How to use it: Server-site, create-swank-server has a new keyword argument :af, which defaults to :inet, and can also be :local * (swank:create-inet-server "/home/dan/.swank/socket" :af :local) Client-side, slime-connect is renamed to slime-connect/inet, and there's a new function (slime-connect/local pathname) M-x slime-connect /home/dan/.swank/socket RET or from another machine M-x slime-connect me@lisp.example.com:/home/dan/.swank/socket RET Opinions? You can get attachtty as part of detachtty, in Debian, FreeBSD ports, or from http://www.cliki.net/detachtty -dan -- http://web.metacircles.com/ - Open Source software development and support

8 14