Hi everyone,
I've noticed a couple of bugs in the most recent version of slime:
1. If I type #\Sp<Tab> in the REPL, I get the message "string=: Symbol's function definition is void: dbgmsg". The following change in `slime-contextual-completions' seems to fix it:
diff -r1.11 slime-c-p-c.el 131c131 < (string= (dbgmsg (subseq token 0 2)) "#\")) ---
(string= (subseq token 0 2) "#\\"))
2. The documentation for `slime-maybe-show-compilation-log' says that it displays the compilation log if compilation fails or if "NOTES is non-NIL". That doesn't match its behaviour; in the current CVS version, it shows the compilation log only if compilation has failed. Is this intended? If not, the following simple change fixes it:
diff -r1.1217 slime.el 2957c2957 < (unless successp ---
(when (or (null successp) notes)
Thanks, James
James Wright james@chumsley.org writes:
Hi everyone,
I've noticed a couple of bugs in the most recent version of slime:
- If I type #\Sp<Tab> in the REPL, I get the message "string=:
Symbol's function definition is void: dbgmsg". The following change in `slime-contextual-completions' seems to fix it:
diff -r1.11 slime-c-p-c.el 131c131
< (string= (dbgmsg (subseq token 0 2)) "#\"))
(string= (subseq token 0 2) "#\\"))
My bad again.