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

[slime-devel] Standard output no longer appears in REPL
by Steven E. Harris 25 Jun '11

25 Jun '11

It's been a couple of months since I last used SLIME. Today I noticed that when I evaluate expressions in the REPL that write to *standard-output*, the output appears in the *inferior-lisp* buffer, but not in the REPL as it used to. I'm using GNU Emacs on Windows atop the CLISP Cygwin build. SLIME is up to date with CVS. Is there some new configuration required to restore the old behavior with output streams feeding into the REPL output? -- Steven E. Harris

5 12

[slime-devel] Slime vs Franz Eli
by Chris Kim 13 Apr '11

13 Apr '11

Hi, all, I've been using Slime on top of Franz ACL for quite a while. My experience with Slime is very positive and I like Slime better in every aspects except in following situations. 1. Slime debugger: It prints bunch of Slime (swank: ..... ) related messages that I'm not interested. It's always hard to trying to comb through messages that I'm interested. How can I turn Slime related messages off? 2. While debugging, evaulating expression does not print anything but only the retuned result. Can I have it print to the standard output, i.e., console? 3. Lack of REPL command: Franz Eli supports REPL commands, for example, ":proc" for listing processes, ":pa" to change package and so on. Is there way to add them in? Thank you very much and I appreciate your efforts making Slime the best list-emacs interface. -chris

6 14

[slime-devel] contrib for repl images
by Christophe Rhodes 08 Oct '10

08 Oct '10

Hi, Attached are files which I propose to add to contrib/ to allow image display in the repl. The Common Lisp support is entirely non-existent, but I have prototype code using the slime support to do manipulations of graphical objects in R: <http://doc.gold.ac.uk/~mas01cr/tmp/swankr-images.png> displays an example. I'd like to put this or something like it in; I'm asking for review of this approach and implementation. Cheers, Christophe

4 4

[slime-devel] Slime presentation marker bug
by Nathan Bird 04 Oct '10

04 Oct '10

I put a test case here that documents it: http://paste.lisp.org/+2GLO The issue is that when it starts a presentation it saves a marker, but then that marker gets moved when printing text and so when it ends the presentation the start and end markers are the same point, the one immediately after the text we are trying to present. I'm not sure where to go from here. I don't know how to get the old marker to stay in place any more than it is now. There is a comment: ;; We use markers because text can also be inserted before this presentation. ;; (Output arrives while we are writing presentations within REPL results.) Perhaps that is more relevant to printing with the target :repl-result vs target null? I tried changing the presentation start function (it's on the paste) to save the number if target is null and that looks like it is mostly working for me, can anyone else comment on the idea? -- Nathan Bird nathan(a)acceleration.net http://www.acceleration.net/ Custom Programming, Design, Hosting, and Broadband.

2 10

[slime-devel] slime-interactive-eval into kill ring
by Tamas K Papp 01 Oct '10

01 Oct '10

Hi, C-x C-e (slime-interactive-eval) prints the value(s) in the minibuffer. Prefixed with C-u, it is inserted in the current buffer. Is there a way to insert it somewhere else? Ideally, it would be very handy to have a way to just save the result in the kill ring, then I could yank it later. Thanks, Tamas

2 5

[slime-devel] suggestion: make applying indent-sexp to results of macroexpansion optional
by michaelawells 01 Oct '10

01 Oct '10

In some cases, "indent-sexp" can be very slow, particularly when it is used on complex "macroexpanded" expressions. In my case, it takes 43 seconds to apply "indent-sexp" to a buffer of ~6000 lines. (I measured this using the elp package. The expression produced by SBCL and Allegro is already nicely formatted, so I would prefer not to display the result as formatted, rather than wait. So, I suggest adding an option to slime.el called "slime-indent-sexp-after-macroexpand", which would allow "indent-sexp" to be disabled. --- slime.el 22 Sep 2010 19:17:35 -0000 1.1340 +++ slime.el 24 Sep 2010 04:23:29 -0000 @@ -150,6 +150,13 @@ :prefix "slime-" :group 'slime) +(defcustom slime-indent-sexp-after-macroexpand t + "Perform 'indent-sexp' before presenting results of macroexpansion. +If disabled, macroexpansion will be presented as formated by the Lisp +in use." + :type 'boolean + :group 'slime-ui) + (defcustom slime-truncate-lines t "Set `truncate-lines' in popup buffers. This applies to buffers that present lines as rows of data, such as @@ -4942,7 +4949,7 @@ (erase-buffer) (insert expansion) (goto-char (point-min)) - (indent-sexp) + (when slime-indent-sexp-after-macroexpand (indent-sexp)) (font-lock-fontify-buffer))) (defun slime-create-macroexpansion-buffer () @@ -4976,8 +4983,8 @@ (goto-char start) (delete-region start end) (insert expansion) - (goto-char start) - (indent-sexp) + (goto-char start) + (when slime-indent-sexp-after-macroexpand (indent-sexp)) (goto-char point)))))))) (defun slime-macroexpand-1 (&optional repeatedly)

3 2

[slime-devel] Lisp connection closed unexpectedly
by J. Bromley 27 Sep '10

27 Sep '10

I am having a problem with SLIME getting disconnected from the Lisp process when requiring certain libraries. I am using clbuild to manage my Lisp implementation and SLIME itself. The problem is that when I do (require 'cl-opengl) in SLIME, I get the message "Lisp connection closed unexpectedly: connection broken by remote peer" in the mini-buffer area. I set swank:*log-events* to t and tried, and unfortunately that was not terribly helpful. Here are the lines generated by the require cl-opengl line: ===== dispatch-event: (:EMACS-REX (SWANK:OPERATOR-ARGLIST "require" "COMMON-LISP-USER") "COMMON-LISP-USER" :REPL-THREAD 15) send-event: #<SB-THREAD:THREAD "repl-thread" RUNNING {10030E2AE1}> (:EMACS-REX (SWANK:OPERATOR-ARGLIST "require" "COMMON-LISP-USER") "COMMON-LISP-USER" 15) wait-for-event: (COMMON-LISP:OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) NIL dispatch-event: (:RETURN #<SB-THREAD:THREAD "repl-thread" RUNNING {10030E2AE1}> (:OK "(require MODULE-NAME &OPTIONAL PATHNAMES)") 15) encode-message decode-message dispatch-event: (:EMACS-REX (SWANK:LISTENER-EVAL "(require 'cl-opengl) ") "COMMON-LISP-USER" :REPL-THREAD 16) send-event: #<SB-THREAD:THREAD "repl-thread" RUNNING {10030E2AE1}> (:EMACS-REX (SWANK:LISTENER-EVAL "(require 'cl-opengl) ") "COMMON-LISP-USER" 16) /Users/jay/Applications/clbuild/clbuild: line 450: 11820 Trace/BPT trap ${lisp} $common_options $eval "$require_asdf" $eval "$set_central_registry" $eval "$EXTRA_CLIM_FEATURES" "$@" Process inferior-lisp exited abnormally with code 133 ===== I am using the following software: * Mac OS X 10.6.4 * SBCL 1.0.42.52 (checked out by clbuild and built) * GNU Emacs 23.1.50.1 (x86_64-apple-darwin10.2.0, NS apple-appkit-1038.25) from MacPorts * SLIME from CVS via clbuild * cl-opengl from git via clbuild I have looked at line 450 of clbuild and it is just the call to launch SBCL. I find no more information about the Trace/BPT trap. I have also tried to find the meaning of the exit code, but have been unsuccessful. If I run clbuild lisp (which runs SBCL without SLIME) the require works fine. Obviously, SLIME provides a much nicer working environment, so it would be great to get it working. I would greatly appreciate any suggestions on possible solutions or about how to debug this further. Thanks and regards, -- Jay Bromley | jbromley at gmail dot com

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 27 Sep '10

27 Sep '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.422 slime/contrib/ChangeLog:1.423 --- slime/contrib/ChangeLog:1.422 Wed Sep 22 15:17:35 2010 +++ slime/contrib/ChangeLog Sun Sep 26 14:10:33 2010 @@ -1,3 +1,8 @@ +2010-09-26 Stas Boukarev <stassats(a)gmail.com> + + * slime-repl.el (slime-repl-history-pattern): Match \t too, + besides \ and \n. + 2010-09-22 Stas Boukarev <stassats(a)gmail.com> * slime-repl.el: Handle (:abort condition) message from lisp.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 23 Sep '10

23 Sep '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2142 slime/ChangeLog:1.2144 --- slime/ChangeLog:1.2142 Mon Sep 20 12:09:13 2010 +++ slime/ChangeLog Wed Sep 22 15:17:35 2010 @@ -1,3 +1,15 @@ +2010-09-22 Stas Boukarev <stassats(a)gmail.com> + + * swank.lisp (eval-for-emacs): Send (:abort condition) where + condition is a condition which was aborted instead of just (:abort). + * slime.el: Handle the above change. + +2010-09-22 Stas Boukarev <stassats(a)gmail.com> + + * swank-clisp.lisp (*external-format-to-coding-system*): Remove + stray :latin-1 argument for ext:make-encoding. + Reported by Mirko Vukovic. + 2010-09-20 Stas Boukarev <stassats(a)gmail.com> * swank-cmucl.lisp (character-completion-set): Implement. Requires Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.421 slime/contrib/ChangeLog:1.422 --- slime/contrib/ChangeLog:1.421 Sat Sep 18 16:47:29 2010 +++ slime/contrib/ChangeLog Wed Sep 22 15:17:35 2010 @@ -1,3 +1,7 @@ +2010-09-22 Stas Boukarev <stassats(a)gmail.com> + + * slime-repl.el: Handle (:abort condition) message from lisp. + 2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> * slime-parse.el (slime-parse-form-upto-point): Fix lp#627308.

1 0

[slime-devel] *external-format-to-coding-system* defvar contents in swank-clisp.lisp
by Mirko Vukovic 22 Sep '10

22 Sep '10

swank-clisp.lisp (defvar *external-format-to-coding-system* ...) has the following line: ((:charset "iso-8859-1" :latin-1) "latin-1" "iso-latin-1" "iso-8859-1") Is the car correct? It is used as an argument to ext:make-encoding in (defimplementation find-external-format (coding-system) ...) and it does not satisfy its lambda list (see http://clisp.cons.org/impnotes/encoding.html#make-encoding) Mirko

2 1

[slime-devel] how to use utf-8, iso-8859-1 with clisp
by Mirko Vukovic 22 Sep '10

22 Sep '10

Hello, (this is with clisp 2.48 on cygwin + windows XP and slime ) I can start up clisp on my laptop with utf-8 and iso-8859-1 encodings (clisp -E utf-8, for example) However, setting `slime-net-coding-system' to utf-8 or iso-8859-1 gives a slime start-up error since the allowed encodings are utf-8-UNIX, iso-8859-1-UNIX (capitalization mine). I can easily change that in `slime-net-valid-coding-systems'. But what is going on here? Thanks, Mirko

2 4

[slime-devel] Daily ChangeLog diff
by Helmut Eller 21 Sep '10

21 Sep '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2141 slime/ChangeLog:1.2142 --- slime/ChangeLog:1.2141 Sat Sep 18 05:34:05 2010 +++ slime/ChangeLog Mon Sep 20 12:09:13 2010 @@ -1,3 +1,9 @@ +2010-09-20 Stas Boukarev <stassats(a)gmail.com> + + * swank-cmucl.lisp (character-completion-set): Implement. Requires + recent versions of CMUCL. + Patch by Raymond Toy. + 2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-backend.lisp (valid-function-name-p): New interface.

1 0

[slime-devel] Updated character completion for cmucl
by Raymond Toy 20 Sep '10

20 Sep '10

Here is an updated version of character completion for cmucl. Major change is that the handling of Hangul syllables and CJK Unified Ideographs is much better and in addition to the Unicode names, the standard character names that were recognized by cmucl are still recognized. The changes are attached. As before, the changes can be just added to the end of swank-cmucl.lisp.

3 6

[slime-devel] Detecting inferior lisp
by Ilya Sterin 20 Sep '10

20 Sep '10

I'm using slime with both sbcl and clojure. In clojure I'm running a swank clojure server and using slime-connect to connect to it. I have different options that need to be set like (slime-setup ...) depending on whether I'm connected to sbcl or clojure. For now I have defined two functions, slime-sbcl and slime-clojure and all happens there, but I'm wondering if there is some sort of a hook and predicate I can use in order to assert the inferior lisp at runtime. Thanks. Ilya

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 19 Sep '10

19 Sep '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2138 slime/ChangeLog:1.2141 --- slime/ChangeLog:1.2138 Fri Sep 3 18:29:43 2010 +++ slime/ChangeLog Sat Sep 18 05:34:05 2010 @@ -1,3 +1,31 @@ +2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-backend.lisp (valid-function-name-p): New interface. + (compiler-macroexpand-1): Use it to guard against type errors + from COMPILER-MACRO-FUNCTION. + +2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (before-init): push :SWANK to *FEATURES*. (lp#627313) + +2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + Make C-c C-m also expand compiler macros. (lp#638720) + + * slime.el (slime-macro/compiler-macro-expand-1): New. + (slime-macro/compiler-macro-expand-1-inplace): New. + (slime-editing-keys): Map `C-c C-m' to first above. + (slime-compiler-macroexpand-1): Take prefix-arg like others. + (slime-compiler-macroexpand-1-inplace): Ditto. + (slime-compiler-macroexpand): Thus deleted. + (slime-compiler-macroexpand-inplace): Ditto. + + * swank.lisp (swank-macro/compiler-macro-expand-1): New defslimefun. + (swank-macro/compiler-macro-expand): New defslimefun. + (macro/compiler-macro-expand-1): New. + (macro/compiler-macro-expand): New. + (expand-repeatedly): New helper. + 2010-09-03 Stas Boukarev <stassats(a)gmail.com> * slime.el (slime-forward-cruft): Use " \t\n" to match whitespaces Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.419 slime/contrib/ChangeLog:1.421 --- slime/contrib/ChangeLog:1.419 Fri Sep 17 16:32:55 2010 +++ slime/contrib/ChangeLog Sat Sep 18 16:47:29 2010 @@ -1,3 +1,21 @@ +2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-parse.el (slime-parse-form-upto-point): Fix lp#627308. + + * slime-autodoc.el (slime-canonicalize-whitespace): New + helper. Extracted out of `slime-format-autodoc'. + (slime-autodoc-to-string): New helper. + (slime-check-autodoc-at-point): Use it. + (autodoc.1): Add test case for above fix. + +2010-09-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-arglist.lisp (function-exists-p): Renamed from + FUNCTION-EXISTS-P. Uses new SWANK-BACKEND:VALID-FUNCTION-NAME-P + underneath. + (valid-operator-name-p): Unused, hence deleted. + (boundp-and-interesting): Renamed from INTERESTING-VARIABLE-P. + 2010-09-17 Stas Boukarev <stassats(a)gmail.com> * swank-sprof.lisp (filter-swank-nodes): Filter other swank

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 18 Sep '10

18 Sep '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.418 slime/contrib/ChangeLog:1.419 --- slime/contrib/ChangeLog:1.418 Thu Sep 16 15:19:26 2010 +++ slime/contrib/ChangeLog Fri Sep 17 16:32:55 2010 @@ -1,3 +1,8 @@ +2010-09-17 Stas Boukarev <stassats(a)gmail.com> + + * swank-sprof.lisp (filter-swank-nodes): Filter other swank + packages too, not only SWANK. + 2010-09-16 Stas Boukarev <stassats(a)gmail.com> * swank-arglists.lisp (print-variable-to-string): Use

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 17 Sep '10

17 Sep '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.416 slime/contrib/ChangeLog:1.418 --- slime/contrib/ChangeLog:1.416 Thu Sep 9 04:28:21 2010 +++ slime/contrib/ChangeLog Thu Sep 16 15:19:26 2010 @@ -1,3 +1,16 @@ +2010-09-16 Stas Boukarev <stassats(a)gmail.com> + + * swank-arglists.lisp (print-variable-to-string): Use + without-printing-errors when printing the value. + Reported by Tobias C. Rittweiler on lp#628945. + +2010-09-16 Christophe Rhodes <csr21(a)cantab.net> + + Image display support for the REPL. + + * slime-media.el: New file. + * swank-media.lisp: New file. + 2010-09-09 Stas Boukarev <stassats(a)gmail.com> * swank-c-p-c.lisp (longest-compound-prefix): Wrong arguments for

1 0

[slime-devel] Character completion for cmucl
by Raymond Toy 17 Sep '10

17 Sep '10

Here is support for character name completion for cmucl. The attached file can be placed at the end of swank-cmucl.lisp. This code will go into the next snapshot of cmucl, so the bulk of the code is conditionalized on lisp::unicode-complete not existing. Because the name space is so large, completion is done kind of incrementally. (If full completion were done, think of how many completions there would be for #\CJK!) The name is completed upto the next "piece". As you type more, more pieces are added. The completions might look a little weird, but they (usually) expand to the correct value eventually. (This is an artifact of how cmucl stores the character names and the desire to do this incrementally.) There's at least one bug: #\ne shows NE as a completion, but that's not a valid name. But the completion also shows the valid continuations. I hope this is useful to someone. Ray

1 2

[slime-devel] C-C C-m both for macro and compiler-macro expansion
by Tobias C Rittweiler 15 Sep '10

15 Sep '10

Would anyone mind, or find it utterly confusing, if C-c C-m would try to expand compiler macros? -T.

2 1

[slime-devel] q on slime-to-lisp-filename-function
by Mirko Vukovic 15 Sep '10

15 Sep '10

Hi, I updated slime to 2010-09-09 from 2010-04-something, and I was unable to start swank because of the following error: PARSE-NAMESTRING: syntax error in filename "C:\\program files\\emacs23.1\\...swank.lisp" at position 2 I was able to fix it by setting slime-to-lisp-filename-function to #'identity (based on an old post from 2008). Is that the correct fix? Thanks, Mirko

2 1

[slime-devel] [CfP] 4th European Lisp Symposium, Hamburg, March 31 - April 1st, 2011
by Didier Verna 13 Sep '10

13 Sep '10

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4th European Lisp Symposium Special Focus on Parallelism & Efficiency March 31 - April 1st, 2011 TUHH, Hamburg University of Technology Hamburg, Germany http://www.european-lisp-symposium.org/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Important Dates ~~~~~~~~~~~~~~~~ + Submission Deadline: January 09, 2011 + Author Notification: February 06, 2011 + Final Paper Due: February 28, 2011 + Symposium: March 31 - April 1st, 2011 Authors of accepted research contributions will be invited to submit an extended version of their papers for journal publication. Scope ~~~~~~ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket and so on. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2011 invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. This year's focus will be directed towards "Parallelism & Efficiency". We especially invite submissions in the following areas: + Parallel and distributed computing + Code generation for multi-core architectures + Code generation for HTM + Large and ultra-large systems + Optimization techniques + Embedded applications Contributions are also welcome in other areas, including but not limited to: + Context-, aspect-, domain-oriented and generative programming + Macro-, reflective-, meta- and/or rule-based development approaches + Language design and implementation + Language integration, inter-operation and deployment + Development methodologies, support and environments + Educational approaches and perspectives + Experience reports and case studies Technical Program: ~~~~~~~~~~~~~~~~~~ We invite submissions in the following forms: * Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. * Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. * Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. * Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates http://www.acm.org/about/class/1998 Submissions should be uploaded to Easy Chair, at the following address: http://www.easychair.org/conferences/?conf=els2011 Programme Chair ~~~~~~~~~~~~~~~~ Didier Verna - EPITA Research and Development Laboratory, France Local Chair ~~~~~~~~~~~~ Ralf Moeller - Hamburg University of Technology, Germany Programme Committee ~~~~~~~~~~~~~~~~~~~~ Antonio Leitao - Instituto Superior Tecnico/INESC-ID, Portugal Christophe Rhodes - Goldsmiths College, University of London, UK David Edgar Liebke - Relevance Inc., USA Didier Verna - EPITA Research and Development Laboratory, France Henry Lieberman - MIT Media Laboratory, USA Jay McCarthy - Brigham Young University, USA Jose Luis Ruiz Reina - Universidad de Sevilla, Spain Marco Antoniotti - Universita Milano Bicocca, Italy Manuel Serrano - INRIA, France Michael Sperber - DeinProgramm, Germany Pascal Costanza - Vrije Universiteit of Brussel, Belgium Scott McKay - ITA Software, USA -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 10 Sep '10

10 Sep '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.415 slime/contrib/ChangeLog:1.416 --- slime/contrib/ChangeLog:1.415 Mon Sep 6 23:05:17 2010 +++ slime/contrib/ChangeLog Thu Sep 9 04:28:21 2010 @@ -1,3 +1,9 @@ +2010-09-09 Stas Boukarev <stassats(a)gmail.com> + + * swank-c-p-c.lisp (longest-compound-prefix): Wrong arguments for + longest-common-prefix. + Reported by Peter Stirling. + 2010-09-07 Stas Boukarev <stassats(a)gmail.com> * swank-c-p-c.lisp: s/delimeter/delimiter/, correct spelling.

1 0

[slime-devel] [investigation] Font lock, reader macros and SLIME repl
by Anton Kovalenko 09 Sep '10

09 Sep '10

Hello SLIME developers, Both in the lisp-mode and in slime REPL, there is currently one major thing that Emacs isn't getting right: constructs using reader macros like #P"/home/" and #2A((1 0) (0 1)) are regarded as two sexps instead of one. E.g. command for wrapping a sexp may turn #P"/home/" into (#P)"/home/", etc. It gets even more awful with paredit-mode (that I prefer to use), but the problem is noticeable even without it. I have investigated one possible solution to it, and here are the results. First, I decided to limit the scope of solution to some predefined "shape" of reader macro: for starters, when #\# is used as dispatch macro character, and its reader function calls READ to get the sexp following #[numarg]<char>. This is the case with all standard reader-macros and many implementation-specific and user-defined ones. Furthermore, I discarded the possibility to consult SWANK for the buffer's *readtable* (SWANK doesn't *know* it, anyway). To get right behavior for #P, #2A and the like, the most appropriate syntax for all macro-characters seems to be `expression prefix': we want Emacs to regard the whole #P thing as it would regard a quote, backquote or comma. Let's use the feature of font-lock mode in modern emacsen: syntactic keywords (in a nutshell, it's when a code used for text-coloring is [ab]used to add syntax-table properties to some text fragments). `parse-sexp-lookup-properties' set to true causes the sexp machinery to look into syntax-table properties of individual characters. Let's add a syntactic keyword to lisp-mode: (defun aak:add-lisp-reader-macros-syntactic-keyword () "Register # numarg macro-character as a font lock syntactic keyword, turning it into expression prefix." (set (make-local-variable 'parse-sexp-lookup-properties) t) (set (make-local-variable 'font-lock-syntactic-keywords) '(("\$\\W\\|$\$\\#\$[0-9]*[A-Za-z]\$" (2 "'"))))) (add-hook 'lisp-mode-hook 'aak:add-lisp-reader-macros-syntactic-keyword) With the hook above, any lisp-mode buffer with font-lock mode enabled gets good enough navigation/wrapping/unwrapping for previously misinterpreted items. I decided to leave macro-characters handled by this regexp to [A-Za-z], because normal behavior of reading the following sexp can't really be expected from other characters: readtable additions along the lines of #"something" and #{something} are also popular, and we can't get _them_ right without knowing a concrete syntaxt they expect. Another decision that has its merits is to limit it further to _standard_ macro-characters only. Now I wanted the same thing to be active for slime-repl mode. The only obstacle was that slime-repl mode is currently font-lock-unfriendly: when some faces are set programmatically and some left to font-lock, the programmatically-set faces should use font-lock-face property instead of face property (the latter gets overridden by font-lock results). A workaround that I use currently is the following advice to add-text-properties: (defadvice add-text-properties (before aak:slime-propertize-with-font-lock-face activate) (when (eq 'slime-repl-mode major-mode) (let* ((props (ad-get-arg 2)) (face (getf props 'face))) (when face (push face props) (push 'font-lock-face props) (when (memq 'face (getf props 'rear-nonsticky)) (push 'font-lock-face (getf props 'rear-nonsticky))) (ad-set-arg 2 props))))) When in slime-repl mode, it copies face property to font-lock-face property, and also makes it rear-nonsticky when face is requested to be. It's the only part that really touches SLIME, and I think it would better insert font-lock-face property itself, together with face property (don't forget rear-nonstickyness). This duplication (face => font-lock-face) does no harm when font-lock mode is disabled, but enables slime-repl buffer to be used with font-lock enabled as well. Another hook to enable font-lock mode in slime buffers: (defun aak:enable-font-lock-for-slime-repl () "Enable font lock mode in slime REPL buffer." (font-lock-fontify-buffer) ;; don't know why it's needed.. (font-lock-mode 1)) (add-hook 'slime-repl-mode-hook 'aak:add-lisp-reader-macros-syntactic-keyword) (add-hook 'slime-repl-mode-hook 'aak:enable-font-lock-for-slime-repl) NB. The problem that I'm trying to solve is even more important for slime-repl buffers, where incorrect sexp wrapping tends to break _presentations_ apart. -- Regards, Anton Kovalenko +7(916)345-34-02 | Elektrostal' MO, Russia

4 7

[slime-devel] C-c tab Completion
by Peter Stirling 09 Sep '10

09 Sep '10

Hi, I use the C-c tab completion from slime-fancy, but after updating slime tonight I get a stack trace like the following when I try to expand e.g.: hun -> hunchentoot: (This is running on sbcl 1.0.42.25) invalid number of arguments: 2 [Condition of type SB-INT:SIMPLE-PROGRAM-ERROR] Restarts: 0: [*ABORT] Return to SLIME's top level. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {AFDBD51}>) Backtrace: 0: (SWANK::LONGEST-COMMON-PREFIX ("hunchentoot" "hunchentoot:"))[:EXTERNAL] 1: (SWANK::LONGEST-COMPOUND-PREFIX ("hunchentoot-asd:" "hunchentoot:") #\-) 2: (SWANK:COMPLETIONS "hun" "MUSIC") 3: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:COMPLETIONS "hun" '"MUSIC") #<NULL-LEXENV>) 4: (SWANK:EVAL-FOR-EMACS (SWANK:COMPLETIONS "hun" '"MUSIC") "MUSIC" 78) 5: (SWANK::PROCESS-REQUESTS NIL) 6: ((LAMBDA ())) 7: ((LAMBDA ())) 8: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {AFE50A5}>) 9: ((FLET SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {AFE50A5}>) 10: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-OUTPUT* . #1=#) (*STANDARD-INPUT* . #) (*TRACE-OUTPUT* . #1#) (*ERROR-OUTPUT* . #1#) (*DEBUG-IO* . #2=#) (*QUERY-IO* . #2#) ...) #<CLOSURE (LAMBDA #) {AFE50B5}>) 11: (SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {CE81349}> NIL) 12: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA #) {AFE5085}>) 13: ((FLET #:WITHOUT-INTERRUPTS-BODY-[BLOCK362]367)) 14: ((FLET SB-THREAD::WITH-MUTEX-THUNK)) 15: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]300)) 16: (SB-THREAD::CALL-WITH-MUTEX ..) 17: (SB-THREAD::INITIAL-THREAD-FUNCTION) 18: ("foreign function: call_into_lisp") 19: ("foreign function: funcall0") 20: ("foreign function: new_thread_trampoline") 21: ("foreign function: #xB7FB796E")

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 07 Sep '10

07 Sep '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.413 slime/contrib/ChangeLog:1.415 --- slime/contrib/ChangeLog:1.413 Fri Sep 3 20:32:14 2010 +++ slime/contrib/ChangeLog Mon Sep 6 23:05:17 2010 @@ -1,3 +1,13 @@ +2010-09-07 Stas Boukarev <stassats(a)gmail.com> + + * swank-c-p-c.lisp: s/delimeter/delimiter/, correct spelling. + +2010-09-07 Stas Boukarev <stassats(a)gmail.com> + + * swank-c-p-c.lisp (untokenize-completion): Take an optional + argument "delimiter". + (longest-compound-prefix): Pass delimiter to untokenize-completion. + 2010-09-04 Stas Boukarev <stassats(a)gmail.com> * swank-fuzzy.lisp (*fuzzy-completion-...*): Change defparameter

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel September 2010