slime-devel April 2004

slime-devel@common-lisp.net

40 participants
103 discussions

[slime-devel] SIGIO vs. FD-HANDLER
by Luke Gorrie 15 Apr '04

15 Apr '04

Ahoy, In CMUCL and non-threads SBCL we default to using a 'SIGIO' signal handler to read and execute requests from Emacs. This means that Lisp is interrupted to immediately serve requests as soon as Emacs sends them. It is convenient, but it has potential to cause unpredictable problems. For me this has been working perfectly, but I've been hearing reports that some people are having stability problems. If you're using CMUCL or non-threads SBCL and are finding Lisp unstable under SLIME, please try adding this to your ~/.swank.lisp: (setq swank:*communication-style* :fd-handler) That way we use the select()-loop instead of signals. It ought to be very safe, though Lisp will only process requests from Emacs when it's otherwise idle. If this solves a problem for you then please let us know. Currently I'm not sure whether SIGIO or FD-HANDLER makes the better default. NB: This stuff is covered in the manual under Lisp-Side configuration. Cheers, Luke

1 0

[slime-devel] Causing slime to enter the debugger
by Thomas F. Burdick 15 Apr '04

15 Apr '04

I'm adding some signal handlers to an application I'm writing, so it acts like a well-behaved Unix daemon. It would be nice to do something like: (defun handle-sighup (&rest ignore) (declare (ignore ignore)) #+debug (cerror "Restart server" "Signal request to restart") (shutdown) (read-configuration) (startup)) The problem is that if I call break from a signal handler, the normal SBCL toplevel enters the debugger. With the following patch, I can set *debugger-hook* to swank:swank-debugger-hook at the toplevel: --- swank.lisp.~1.166.~ Thu Apr 8 16:41:05 2004 +++ swank.lisp Wed Apr 14 18:37:54 2004 @@ -14,6 +14,7 @@ #:create-swank-server #:ed-in-emacs #:print-indentation-lossage + #:swank-debugger-hook ;; configurables #:*sldb-pprint-frames* #:*communication-style* @@ -882,7 +883,8 @@ *package*)) (*sldb-level* (1+ *sldb-level*)) (*swank-state-stack* (cons :swank-debugger-hook *swank-state-stack*)) - (*print-readably* nil)) + (*print-readably* nil) + (*emacs-connection* (or *emacs-connection* (default-connection)))) (force-user-output) (call-with-debugging-environment (lambda () (sldb-loop *sldb-level*)))))

2 1

[slime-devel] [BUG] Completions for "," commands doesn't work
by Ivan Boldyrev 15 Apr '04

15 Apr '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First, when I press comma just after Slime start, it works as self-insert char, not as command. When I press <ENTER> and press comma in new REPL line, Emacs asks me a command. But autocompletion doesn't work: for example, when I press <TAB> to see a list of available completions, I see error message: PC-do-completion: Wrong type argument: listp, "force-compile-system" Here is stack trace: Debugger entered--Lisp error: (wrong-type-argument listp "force-compile-system") all-completions("" ("force-compile-system" "compile-system" "load-system" "force-load-system" "compile-and-load" "defparameter" "!" "sayoonara" "resend-form" "pop-package" "-p" "push-package" "+p" "change-package" "!p" "pop-directory" "-d" "push-directory" "+d" "change-directory" "!d" "help" "?") nil) PC-do-completion(nil) PC-complete() call-interactively(PC-complete) completing-read("Command: " ("force-compile-system" "compile-system" "load-system" "force-load-system" "compile-and-load" "defparameter" "!" "sayoonara" "resend-form" "pop-package" "-p" "push-package" "+p" "change-package" "!p" "pop-directory" "-d" "push-directory" "+d" "change-directory" "!d" "help" "?") nil t nil slime-repl-shortcut-history) (slime-lookup-shortcut (completing-read "Command: " (slime-list-all-repl-shortcuts) nil t nil (quote slime-repl-shortcut-history))) (let ((command-spec ...)) (call-interactively (cdr ...))) (if (save-excursion (goto-char slime-repl-input-start-mark) (looking-at " *$")) (let (...) (call-interactively ...)) (insert (string slime-repl-shortcut-dispatch-char))) slime-handle-repl-shortcut() call-interactively(slime-handle-repl-shortcut) As I understand, second argument of all-completions is assoc. list, not just list of strings (and documentation string for this function states the same). GNU Emacs 21.3.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2003-09-20 on localhost Slime was fetched from CVS last night (HEAD revision). - -- Ivan Boldyrev Violets are red, Roses are blue. // I'm schizophrenic, And so am I. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.3.5 (GNU/Linux) iQEVAwUBQH4kBA4ALcwzZFpVAQI7aQf8Cqo5wAlUnL6Mxpx85yBSOFY/027iOaLe TsbKT9CFL3qFoyC+lyIHEGLagM+BhMy6HjY1Vx7fwZvIT82etZyq/PWW1ji+Mv/+ 7F0Jqd1ILL17Nfso+gsgG/ayslwGNIKwGO1H2jgEZ72E5H9pbVmwhrSbHPTFDIFg wAfA2FzCrTwvA5Q5wtFuuOOrCYl54e9ZxpbA1Cn1x3Z2ojeE4yd6SFFc5Ah3lea2 WGfyohcxEdT5UdtgEntfp4t0oDBid0YcsWwcv30icclgC0ODq7p9ol3WrL6HPN9n SNFPqXGzRoLGKYQkhmu46Yg6zG9gkWAqW9Dmlq2ssnTpgGydIjHbZA== =m5E+ -----END PGP SIGNATURE-----

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 15 Apr '04

15 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.332 slime/ChangeLog:1.335 --- slime/ChangeLog:1.332 Tue Apr 13 06:04:38 2004 +++ slime/ChangeLog Wed Apr 14 15:15:13 2004 @@ -1,3 +1,22 @@ +2004-04-14 Luke Gorrie <luke(a)bluetail.com> + + * doc/slime.texi (Shortcuts): Described REPL shortcuts. + + * slime.el (slime-oos): Generic ASDF interface. + (force-compile-system, compile-system, load-system, + force-load-system): New REPL commands. + + * swank-backend.lisp (operate-on-system): More generic interface + to ASDF. + + * swank.lisp (operate-on-system-for-emacs): More generic + interface to ASDF. + + * slime.el (slime-repl-mode-map): Portability fix for definition + of the REPL command character. + (slime-maybe-rearrange-inferior-lisp): Bugfix for running + multiple inferior lisps. + 2004-04-13 Marco Baringer <mb(a)bese.it> * slime.el (slime-handle-repl-shortcut,

1 0

[slime-devel] [PATCH] Sorry, new version :)
by Ivan Boldyrev 15 Apr '04

15 Apr '04

-- Ivan Boldyrev Violets are red, Roses are blue. // I'm schizophrenic, And so am I.

1 0

[slime-devel] Patch for problem described above
by Ivan Boldyrev 15 Apr '04

15 Apr '04

Problem was simplier than I expected :) As usually, if you want mention me in ChangeLog, do not mention my e-mail, only name. -- Ivan Boldyrev Your bytes are bitten.

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 14 Apr '04

14 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.331 slime/ChangeLog:1.332 --- slime/ChangeLog:1.331 Fri Apr 9 16:48:13 2004 +++ slime/ChangeLog Tue Apr 13 06:04:38 2004 @@ -1,3 +1,10 @@ +2004-04-13 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-handle-repl-shortcut, + slime-list-all-repl-shortcuts, slime-lookup-shortcut, + defslime-repl-shortcut): Refactor repl shortcut code to provide a + more leggible help. + 2004-04-09 Lawrence Mitchell <wence(a)gmx.li> * slime.el (slime-same-line-p): Use `line-end-position', rather

1 0

[slime-devel] compiler note buffers
by Zach Beane 12 Apr '04

12 Apr '04

I kinda like the compiler notes tree, but it has one thing that bugs me. A little background: I typically use slime by having one emacs window for the file I'm editing, and one emacs window for the slime repl. I don't split between the file and the repl in a single window. I use "C-c C-c" all the time to send the current defun to SBCL; I didn't even know about C-M-x until recently. When I have compiler notes, my source window gets split up. If I "q", the notes disappear and the original layout is restored, but if I don't "q" immediately and another compiler notes tree is triggered, "q" doesn't restore the original layout, the window remains split. What should I do? I tried using a typeout frame, but it doesn't look like the compiler notes tree uses it. Zach

1 0

[slime-devel] Problems with CLISP asserts
by Barry Fishman 12 Apr '04

12 Apr '04

When running the CVS version of CLISP I get a failure during the asserts in slink.lisp. The problem is that: (assert (test-print-arglist '(&key (function #'+)) "(&key (function #'+))")) fails because: (print-arglist-to-string '(&key (function #'+))) Returns: "(&key (function #'|COMMON-LISP|::|+|))" rather than: "(&key (function #'+))" I would think the CLISP response was technically correct, although overly verbose. This seems to be a side effect of using WITH-STANDARD-IO-SYNTAX, and PPRINT. (pprint '#'+) => #'+ (with-standard-io-syntax (pprint '#'+)) => #'|COMMON-LISP|::|+| (with-standard-io-syntax (princ '#'+)) => #'+ -- Barry Fishman

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 10 Apr '04

10 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.330 slime/ChangeLog:1.331 --- slime/ChangeLog:1.330 Thu Apr 8 11:26:44 2004 +++ slime/ChangeLog Fri Apr 9 16:48:13 2004 @@ -1,3 +1,9 @@ +2004-04-09 Lawrence Mitchell <wence(a)gmx.li> + + * slime.el (slime-same-line-p): Use `line-end-position', rather + than searching for a newline manually. + (slime-repl-defparameter): Use VALUE, not VALUE-FORM. + 2004-04-08 Marco Baringer <mb(a)bese.it> * slime.el (slime-repl-package-stack): New buffer local variable.

1 0

← Newer
1
...
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel April 2004