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

[slime-devel] Console raw during a SLIME session
by Sean Charles 10 Dec '06

10 Dec '06

Hi, Can anybody help me out here, I am stuck as I don't know what SLIME does with the I/O once it is running. I am writing a data-entry application, console based, and it must be able to perform read-char without having to press return. To effect this I have had to resort to the following development methodology :- (a) open a new xterm or Terminal.app (OS X 10.4.8) window (b) $ stty cbreak (c) $ sbcl (d) load my code (e) start my application It works just fine, my functions getting a date etc all respond to the correct number of keystrokes but the problem is that it doesn't seem to work from SLIME mode ie the "stty cbreak" doesn't seem to be in force if I execute it from within Emacs. So, does anybody know what I have to do to make it such that a single key press is all I need to get read-char to come back with the keypress inside SLIME+EMACS... it's a bit of a pain having to test it from the shell every time I do something major to the application. is there an even Lispier way of doing this, am I missing something, unaware of something... I have only been using Lisp for about four months now and the size of that HyperSpec still makes my brain hurt ;-) Many thanks, Sean Charles

3 4

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

09 Dec '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1017 slime/ChangeLog:1.1018 --- slime/ChangeLog:1.1017 Thu Dec 7 06:09:46 2006 +++ slime/ChangeLog Fri Dec 8 08:32:45 2006 @@ -1,4 +1,4 @@ -2006-12-07 mb <mb(a)bese.it> +2006-12-07 Marco Baringer <mb(a)bese.it> * swank.lisp (init-inspector): Added eval parameter. If NIL we don't eval FORM but limit our selves to cl:read'ing it and

1 0

[slime-devel] How to debug a crash?
by Harald Hanche-Olsen 08 Dec '06

08 Dec '06

I have a certain Lisp file that appears to be toxic to the emacs/slime combination. If I edit the file while slime is running (by which I just mean there is a slime-repl buffer with an active lisp in it), emacs crashes. If I edit the same file without slime being active, or edit another lisp file in slime's presence, no crash. Also, I get no crash if emacs runs in a terminal. I should mention that the file in question contains some nonstandard lisp syntax. I have a reader macro that reads in something like @2006-12-03 and converts it to a date. But of course, this is harmless if read with standard syntax: It just becomes another symbol. I am somewhat at a loss as to how I can get enough information out of the crash so as to gain some notion about why and how this happens. A bit of background: The slime is from cvs, downloaded in the past few days. The lisp is sbcl 1.0. I am running GNU Emacs 23.0.0, the emacs-unicode-2 branch out of cvs (somewhat stale) on Mac OS X 10.4.8. If I start sbcl in a terminal window, run (swank:create-server :dont-close) and the connect from slime and trigger the bug, this is what I see in the terminal ;; swank:close-connection: end of file on #<sb-sys:fd-stream for "a constant string" {11CFA201}> which I suppose is the expected result if emacs just goes away for any reason. The crash leaves a backtrace in Library/Logs/CrashReporter/emacs.crash.log which could actually be informative, since my emacs is not stripped. I include it below, in case anybody can make sense out of it. But the following excerpt makes me wonder if it is really some incoming data from the superior lisp that is causing the trouble? 37 emacs 0x0015e68c read_process_output + 1236 (process.c:5088) 38 emacs 0x00160fd4 wait_reading_process_output + 4200 (process.c:4697) 39 emacs 0x0000bcd0 sit_for + 216 (dispnew.c:6412) 40 emacs 0x000be990 read_char + 3016 (keyboard.c:2777) 41 emacs 0x000c1b18 read_key_sequence + 2440 (keyboard.c:8872) 42 emacs 0x000c3768 command_loop_1 + 1064 (keyboard.c:1540) Is there an easy way to get a trace of the traffic between emacs and the superior lisp? I know that some such information is traced on the emacs side, but since emacs crashes, I cannot see it there. - Harald ---------------------------------------------------------------- PS. Sorry, but I won't include the toxic file, as it contains information of a private nature. Anyway, here is the full backtrace. Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x0110afff Thread 0 Crashed: 0 emacs 0x00145934 char_quoted + 120 (syntax.c:301) 1 emacs 0x0014ae84 Fbackward_prefix_chars + 604 (syntax.c:2868) 2 emacs 0x00125d8c Ffuncall + 844 (eval.c:2898) 3 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 4 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 5 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 6 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 7 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 8 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 9 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 10 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 11 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 12 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 13 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 14 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 15 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 16 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 17 emacs 0x001259d4 apply_lambda + 248 (eval.c:3013) 18 emacs 0x00125198 Feval + 1312 (eval.c:2283) 19 emacs 0x0012553c Fprogn + 60 (eval.c:432) 20 emacs 0x00128010 Flet + 504 (eval.c:1053) 21 emacs 0x00125280 Feval + 1544 (eval.c:2306) 22 emacs 0x0012553c Fprogn + 60 (eval.c:432) 23 emacs 0x00125888 funcall_lambda + 800 (eval.c:3081) 24 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 25 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 26 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 27 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 28 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 29 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 30 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 31 emacs 0x001571bc Fbyte_code + 2264 (bytecode.c:695) 32 emacs 0x001258b8 funcall_lambda + 848 (eval.c:3088) 33 emacs 0x00125f7c Ffuncall + 1340 (eval.c:2968) 34 emacs 0x00127848 Fapply + 532 (eval.c:2394) 35 emacs 0x001278b4 apply1 + 88 (eval.c:2659) 36 emacs 0x001237ec internal_condition_case_1 + 352 (eval.c:1522) 37 emacs 0x0015e68c read_process_output + 1236 (process.c:5088) 38 emacs 0x00160fd4 wait_reading_process_output + 4200 (process.c:4697) 39 emacs 0x0000bcd0 sit_for + 216 (dispnew.c:6412) 40 emacs 0x000be990 read_char + 3016 (keyboard.c:2777) 41 emacs 0x000c1b18 read_key_sequence + 2440 (keyboard.c:8872) 42 emacs 0x000c3768 command_loop_1 + 1064 (keyboard.c:1540) 43 emacs 0x00123aec internal_condition_case + 344 (eval.c:1474) 44 emacs 0x000b538c command_loop_2 + 64 (keyboard.c:1329) 45 emacs 0x00123660 internal_catch + 256 (eval.c:1211) 46 emacs 0x000b5078 command_loop + 148 (keyboard.c:1311) 47 emacs 0x000b5190 recursive_edit_1 + 176 (keyboard.c:1001) 48 emacs 0x000b5308 Frecursive_edit + 256 (keyboard.c:1063) 49 emacs 0x000b4ba8 main + 4496 (emacs.c:1800) 50 emacs 0x000024d0 _start + 348 (crt.c:272) 51 emacs 0x00002370 start + 60

3 6

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

08 Dec '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1015 slime/ChangeLog:1.1017 --- slime/ChangeLog:1.1015 Wed Dec 6 06:51:00 2006 +++ slime/ChangeLog Thu Dec 7 06:09:46 2006 @@ -1,3 +1,17 @@ +2006-12-07 mb <mb(a)bese.it> + + * swank.lisp (init-inspector): Added eval parameter. If NIL we + don't eval FORM but limit our selves to cl:read'ing it and + inspecting that value. + + * slime.el (slime-inspect): If a prefix argument is provided pass + :eval nil to swank:init-inspector. + +2006-12-07 Paul Collins <paul(a)briny.ondioline.org> + + * hyperspec.el (common-lisp-hyperspec): Strip all text properties + from the symbol-at-point to avoid problems with read-only text. + 2006-12-06 Marco Baringer <mb(a)bese.it> * slime.el (slime-search-buffer-package): Don't call

1 0

Re: [slime-devel] Re: Lisp and real-world...
by Sean Charles 08 Dec '06

08 Dec '06

> Hi Sean, > > Maybe a CLiki page to gather input? I'm interested in answers too. OK, here it is: http://www.cliki.net/Lisp%20Deployment Sean

3 2

[slime-devel] per-slime-dialect slime-connected-hook implementation
by _deepfire＠feelingofgreen.ru 07 Dec '06

07 Dec '06

The following snippet adds support for per-slime-dialect hooks to be called after the connection is established. A subtle point is that this allows for nice customisation of lisp projects to be run: (define-slime-dialect "foo" "sbcl" nil (lambda () (cd "/foo/project/path/") (slime-load-file "load-foo.lisp"))) (define-slime-dialect "bar" "sbcl" nil (lambda () (cd "/path/to/bar/project/") (slime-load-file "load-bar.lisp"))) Granted, this could have been arranged for via parameters to sbcl, effectively making an illusion of two "differeng" lisp implementations, but somehow this just feels... cleaner? (this is against cvs slime) --- slime/slime.el 2006-11-29 04:11:54.000000000 +0300 +++ slime-new/slime.el 2006-11-29 04:07:28.000000000 +0300 @@ -1573,20 +1573,29 @@ (when package (slime-repl-set-package (second package))))))) -(defmacro define-slime-dialect (name &optional program hook) +(defvar *slime-in-dialect* nil) + +(defmacro define-slime-dialect (name &optional program hook connhook) "Define a command slime-dialect-NAME to start a specific Lisp. PROGRAM is the command to start the inferior process. HOOK is function which is run before the process is started." (let ((funsym (intern (format "slime-dialect-%s" name))) (hooksym (intern (format "slime-dialect-%s-hook" name))) + (connhooksym (intern (format "slime-dialect-%s-connected-hook" name))) (progsym (intern (format "slime-dialect-%s-program" name)))) `(progn (defvar ,progsym ,program) (defvar ,hooksym ,hook) + (defvar ,connhooksym ,connhook) + (add-hook 'slime-connected-hook + (lambda () + (when (equal *slime-in-dialect* ,name) + (run-hooks ',connhooksym)))) (defun ,funsym () ,(format "Start up slime according to `%s'." progsym) (interactive) (let ((inferior-lisp-program ,progsym)) + (setq *slime-in-dialect* ,name) (run-hooks ',hooksym) (call-interactively 'slime))))))

9 16

[slime-devel] [PATCH] hyperspec.el: strip text properties from suggestion
by Paul Collins 07 Dec '06

07 Dec '06

When point is just after the slime prompt and the user does M-x hyperspec-lookup, the prompt is inserted into the minibuffer as a suggestion. Text properties are retained, and so the user cannot delete the suggestion or even select the previous history entry. Here is a patch that corrects this problem by stripping all of the text properties from the suggestion. A big hammer, perhaps, but I don't like seeing randomly-coloured text in the minibuffer anyway. Index: hyperspec.el =================================================================== RCS file: /project/slime/cvsroot/slime/hyperspec.el,v retrieving revision 1.10 diff -u -r1.10 hyperspec.el --- hyperspec.el 28 Oct 2006 08:44:41 -0000 1.10 +++ hyperspec.el 6 Dec 2006 21:08:16 -0000 @@ -83,7 +83,9 @@ Visit http://www.lispworks.com/reference/HyperSpec/ for more information. If you copy the HyperSpec to another location, customize the variable `common-lisp-hyperspec-root' to point to that location." - (interactive (list (let* ((symbol-at-point (thing-at-point 'symbol)) + (interactive (list (let* ((symbol-at-point + (substring-no-properties + (thing-at-point 'symbol))) (stripped-symbol (and symbol-at-point (downcase -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood

2 2

[slime-devel] who-calls vs list-callers
by Marco Baringer 07 Dec '06

07 Dec '06

can we drop the list-callers interface and just use who-calls? i don't think slime sholud expose two ways to do the same thing. if we want structure slime's xref implementation in two layers, for whatever technical reasons caused us to have these two functions, i'm fine with that. -- -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] Daily ChangeLog diff
by mbaringer＠common-lisp.net 07 Dec '06

07 Dec '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1013 slime/ChangeLog:1.1015 --- slime/ChangeLog:1.1013 Tue Dec 5 09:36:34 2006 +++ slime/ChangeLog Wed Dec 6 06:51:00 2006 @@ -1,3 +1,16 @@ +2006-12-06 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-search-buffer-package): Don't call + match-string-no-properties if it's not defined (as is on some + xemacs') + (slime-repl-clear-buffer): Added optional prefix argument + specifying how many lines to leave. + +2006-12-06 Johan Bockgård <bojohan+sf(a)dd.chalmers.se> + + * swank.lisp (fuzzy-completion-set): Don't mix for clauses and + body clauses in loop. + 2006-12-05 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (create-swank-server): Removed. Use create-server

1 0

[slime-devel] match-string-no-properties missing?
by Alberto Riva 06 Dec '06

06 Dec '06

Hi, I recently updated to the latest slime from CVS, and now every time I do a M-. I get an emacs message that says "Symbol's function definition is void: match-string-no-properties." My emacs is XEmacs 21.4 (patch 15) (x86_64-redhat-linux, Mule). All help appreciated! Thanks, Alberto Riva University of Florida

4 6