I read this as
Don't show the notes a) if there aren't any b) There are but they all have the location noted
a) makes sense to me b) doesn't. I keep getting a note that there is a warning but then have to switch to the repl to see what it is.
(defun slime-maybe-list-compiler-notes (notes) "Show the compiler notes if appropriate." (unless (or (null notes) (and (eq last-command 'slime-compile-defun) (every #'slime-note-has-location-p notes))) (slime-list-compiler-notes notes)))
-Alan
Alan Ruttenberg alanr-l@mumble.net writes:
I read this as
Don't show the notes a) if there aren't any b) There are but they all have the location noted
Both, a) and b) are intentional.
a) makes sense to me b) doesn't. I keep getting a note that there is a warning but then have to switch to the repl to see what it is.
The reasoning is that with CMUCL/SBCL it is more fun to use M-n/M-p in the source buffer than looking at the notes buffer. If every warning has a location, than all notes can be displayed with M-n/M-p. It's also a bit annoying if the notes buffer pops up all the time, especially when used with C-c C-c.
The notes can still be displayed with M-x slime-list-compiler-notes. Alternatively slime-compilation-finished-hook can be set to a different function.
The note buffer still feels a bit clunky. It would be nice if it where bit smoother in combination with C-c C-c, but I have currently no good ideas.
Helmut.