slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] BUG + PATCH: doc/Makefile uses Bash extensions without setting SHELL=/bin/bash
by Teemu Likonen 11 Jul '09

11 Jul '09

The "clean" target in doc/Makefile uses features of Bash shell, namely brace expansions: rm -f slime.{info,pdf,dvi,ps,html} This feature does not work with POSIX sh shell which the /bin/sh implements and which is the default shell used by "make". In some systems /bin/sh is a symlink to /bin/bash but not in all. For example, in Ubuntu GNU/Linux systems /bin/sh link points to /bin/dash which is very close to POSIX sh. Debian GNU/Linux will switch to /bin/sh -> /bin/dash in their next release. So, to fix the bug you should either do this: --8<---------------cut here---------------start------------->8--- diff --git i/doc/Makefile w/doc/Makefile index 9ea9ebf..38ff658 100644 --- i/doc/Makefile +++ w/doc/Makefile @@ -14,6 +14,9 @@ INSTALL_CMD=install -m 644 # Info files generated here. infofiles=slime.info +# Use Bash shell +SHELL=/bin/bash + TEXI = slime.texi contributors.texi all: slime.info slime.pdf html/index.html --8<---------------cut here---------------end--------------->8--- Or you should stop using Bash extensions in the Makefile: --8<---------------cut here---------------start------------->8--- diff --git i/doc/Makefile w/doc/Makefile index 9ea9ebf..1e68cf5 100644 --- i/doc/Makefile +++ w/doc/Makefile @@ -95,6 +95,8 @@ uninstall-info: clean: rm -f contributors.texi - rm -f slime.{aux,cp,cps,fn,fns,ky,kys,log,pg,tmp,toc,tp,vr,vrs} - rm -f slime.{info,pdf,dvi,ps,html} - rm -rf html{,.tgz} + rm -f slime.aux slime.cp slime.cps slime.fn slime.fns slime.ky + rm -f slime.kys slime.log slime.pg slime.tmp slime.toc slime.tp + rm -f slime.vr slime.vrs + rm -f slime.info slime.pdf slime.dvi slime.ps slime.html + rm -rf html html.tgz --8<---------------cut here---------------end--------------->8--- I suggest doing the latter.

2 1

[slime-devel] SWANK STREAMS clobbered with lispworks
by Madhu 11 Jul '09

11 Jul '09

On Lispworks, the output associated with an editor window goes to the Output Browser pane. So evaluating a line such as (format t "foo~%"), or (format *standard-output* "foo~%") with C-M-x in an editor pane would print "foo" in the Output Browser. However, when using SLIME, once emacs has connected to Lispworks over SWANK, the output starts goes to the terminal on which Lispworks was initially started. This is because the value of *STANDARD-OUTPUT* in the editor pane gets clobbered and set to a Synonym stream to *TERMINAL-IO*. This behaviour is observed on LWL with any version of slime, and is not desirable. How can one get the `output stream' back so output from the Lispworks IDE can be seen inside the IDE ? -- Madhu

6 18

[slime-devel] Daily ChangeLog diff
by Helmut Eller 07 Jul '09

07 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1806 slime/ChangeLog:1.1808 --- slime/ChangeLog:1.1806 Thu Jul 2 13:00:21 2009 +++ slime/ChangeLog Mon Jul 6 08:32:12 2009 @@ -1,3 +1,15 @@ +2009-07-06 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-ecl.lisp (find-external-format): Copied from + swank-sbcl.lisp. A lot of backends seem to share the same + implementation, perhaps some refactoring is needed. + +2009-07-06 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (make-repl-input-stream): Make sure to redirect + output from slime requests to the REPL buffer for + communication-style=NIL. + 2009-07-02 Stas Boukarev <stassats(a)gmail.com> * slime.el (slime-beginning-of-symbol): Limit searching to 2000 @@ -148,7 +160,7 @@ * swank-ecl.lisp: Support new environment changes in recent ECL/CVS patch largely from ECL maintainer. -2009-06-1 Tobias C. Rittweiler <tcr(a)freebits.de> +2009-06-11 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el ([test] font-lock-magic): Moved to fontifying-fu contrib.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 05 Jul '09

05 Jul '09

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.221 slime/contrib/ChangeLog:1.222 --- slime/contrib/ChangeLog:1.221 Thu Jul 2 13:00:25 2009 +++ slime/contrib/ChangeLog Sat Jul 4 05:54:16 2009 @@ -1,3 +1,15 @@ +2009-07-04 Tobias C. Rittweiler <tcr(a)freebits.de> + + Fix font-lock magic for s-code.lisp in the series package. + + * slime-fontifying-fu.el (slime-beginning-of-tlf): Use + `syntax-ppss-toplevel-pos' on GNU Emacs. Old definition is + retained for systems where it's not available. Also wrap an + `ignore-errors' around the call to `up-list' in the old definition + to guard against unbalanced parentheses. + + Reported by Stelian Ionescu, Raymond Toy. + 2009-07-02 Stas Boukarev <stassats(a)gmail.com> * slime-repl.el (slime-repl-delete-current-input): Make it interactive.

1 0

[slime-devel] [NEW] all-logical-hosts
by Terje Norderhaug 03 Jul '09

03 Jul '09

I am making a logical pathname inspector for use with Swank. Common LISP provides #'logical-pathname-translations that works on the name of a logical host. However, it assumes that the developer already know the hostnames. However, Common LISP does not provide a function to get all logical hostnames. I suggest adding a function to Swank to discover the names of all logical hosts. Here is a candidate with implementations for Clozure and LispWorks: ;; swank-backend.lisp (definterface all-logical-hosts () "Return a list of the names of all logical hosts" NIL) ;; swank-openmcl.lisp (defimplementation all-logical-hosts () (mapcar #'car ccl::%logical-host-translations%)) ;; swank-lispworks.lisp (defimplementation all-logical-hosts () (let (result) (maphash (lambda (key value)(push key result)) system::*logical-pathname-translations*) result)) ;; alternatively: (defimplementation all-logical-hosts () (loop for key being the hash-keys of system::*logical-pathname- translations* collect key)) -- Terje Norderhaug

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 03 Jul '09

03 Jul '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1802 slime/ChangeLog:1.1806 --- slime/ChangeLog:1.1802 Thu Jul 2 00:13:10 2009 +++ slime/ChangeLog Thu Jul 2 13:00:21 2009 @@ -1,5 +1,24 @@ 2009-07-02 Stas Boukarev <stassats(a)gmail.com> + * slime.el (slime-beginning-of-symbol): Limit searching to 2000 + characters. + +2009-07-02 Terje Norderhaug <terje(a)in-progress.com> + + * swank-lispworks.lisp (thread-attributes): Implemented. + +2009-07-02 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (ed-in-emacs): Handle symbols/function-names better. + * slime.el (slime-ed): Updated accordingly. + +2009-07-02 Terje Norderhaug <terje(a)in-progress.com> + + * swank.lisp (operator-arglist): Don't use pprint-fill + for people with wide screens. + +2009-07-02 Stas Boukarev <stassats(a)gmail.com> + * slime.el (slime-net-coding-system): make it customizable. (slime-inspector-operate-on-click): Make --more-- button in the inspector clickable. Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.220 slime/contrib/ChangeLog:1.221 --- slime/contrib/ChangeLog:1.220 Sun Jun 28 04:51:18 2009 +++ slime/contrib/ChangeLog Thu Jul 2 13:00:25 2009 @@ -1,3 +1,7 @@ +2009-07-02 Stas Boukarev <stassats(a)gmail.com> + + * slime-repl.el (slime-repl-delete-current-input): Make it interactive. + 2009-06-28 Stas Boukarev <stassats(a)gmail.com> * slime-fuzzy.el (slime-fuzzy-complete-symbol): show message in the

1 0

[slime-devel] [BUG] ed-in-emacs on symbols
by Terje Norderhaug 02 Jul '09

02 Jul '09

The ed-in-emacs function may err when given certain symbols as argument. In particular, multiple escaped characters in a symbol can trip it up. For example, with AquaMacs + Clozure: (ed 'a\ b\ c) => error in process filter: Wrong number of arguments: NIL, 3 (ed-in-emacs '|ab)c|) => error in process filter: No known definition for: common-lisp- user::ab (in nil) The cause is that ed-in-emacs attempts to pass the raw symbol when dispatching :ED to emacs: 1. dispatch-event: (:EMACS-REX (SWANK:LISTENER-EVAL "(ed 'a\\ b\\ c)") "COMMON-LISP-USER" :REPL-THREAD 74) 2. send-event: #<PROCESS repl-thread(36)> (:EMACS-REX (SWANK:LISTENER- EVAL "(ed 'a\\ b\\ c)") "COMMON-LISP-USER" 74) 3. dispatch-event: (:ED COMMON-LISP-USER::|A B C|) 4. WRITE: (:ed common-lisp-user::|A B C|) Common LISP typically outputs a symbol using bars for |multiple escape|. However, this is not understood by the emacs reader. How can we change the encoding of the :ED dispatch symbol argument to fix this issue? -- Terje Norderhaug

2 2

[slime-devel] Fontification error in series/s-code.lisp
by Stelian Ionescu 02 Jul '09

02 Jul '09

$ emacs --version GNU Emacs 23.1.50.1 Warning (slime): "s-code.lisp":921:4 (pt=35805). Caught error when trying to extend the region for fontification. The error was: (cl-assertion-failed (not (plusp (nth 0 (slime-current-parser-state))))) Further: font-lock-beg=35981, font-lock-end=36491. Backtrace: backtrace() slime-bug("Caught error when trying to extend the region for fontification. The error was: %S Further: font-lock-beg=%d, font-lock-end=%d." (cl-assertion-failed (not (plusp ...))) 35981 36491) slime-extend-region-for-font-lock() font-lock-default-fontify-region(35981 36491 nil) font-lock-fontify-region(35981 36491) run-hook-with-args(font-lock-fontify-region 35981 36491) byte-code("\302\303 #\207" [start next run-hook-with-args jit-lock-functions] 4) jit-lock-fontify-now(35981 36481) jit-lock-function(35981) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

1 0

[slime-devel] [PATCH] operator-arglist
by Terje Norderhaug 02 Jul '09

02 Jul '09

The operator-arglist slimefun uses #'pprint-fill to format an arglist without enclosing parentheses. Unfortunately, for longer arglists, a consequence is that the output might be pretty printed based on the output width on the server lisp, potentially leading to unwanted linebreaks and whitespace in the result. For example, using Clozure, evaluate operator-arglist for #'cl:directory: (swank::operator-arglist "DIRECTORY" "COMMON-LISP") => "(DIRECTORY PATH &KEY DIRECTORIES FILES ALL DIRECTORY-PATHNAMES INCLUDE-EMACS-LOCKFILES TEST FOLLOW-LINKS)" Such results may require a cleanup to be presented by the client on one line or with the preferred width. It would be preferable to have the result single spaced and without linebreaks, leaving the formatting to the swank client: "(DIRECTORY PATH &KEY DIRECTORIES FILES ALL DIRECTORY-PATHNAMES INCLUDE-EMACS-LOCKFILES TEST FOLLOW-LINKS)" Here is a patch that writes the function name and arglist as a list on a single line: diff -u slime-2009-06-30/swank.lisp patch/swank.lisp --- slime-2009-06-30/swank.lisp 2009-06-29 00:15:06.000000000 -0700 +++ patch/swank.lisp 2009-06-30 14:04:48.000000000 -0700 @@ -3005,7 +3005,7 @@ (let ((args (arglist (parse-symbol name (guess-buffer-package package)))) (*print-escape* nil)) (cond ((eq args :not-available) nil) - (t (format nil "(~a ~/pprint-fill/)" name args)))))) + (t (princ-to-string (cons name args))))))) -- Terje Norderhaug

2 2

[slime-devel] Lispworks thread-attributes
by Terje Norderhaug 02 Jul '09

02 Jul '09

Here is a candidate implementation of thread-attributes for LispWorks: ; swank-lispworks.lisp (defimplementation thread-attributes (thread) (list :priority (mp:process-priority thread) :idle (mp:process-idle-time thread))) -- Terje Norderhaug

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