On Fri, Nov 2, 2018 at 3:38 PM Neil Van Dyke <[email protected]> wrote:
> * Should such a failing message also have some way of click navigating
> to the test failure in DrRacket, like for exceptions? (Note that the
> answer to the next might be involved.)
Yes please! It is no fun finding a failing test source in an
unfamiliar code base.
I'd suggest writing to stderr the same location format used by rackunit.
That way people in emacs can add to compilation-error-regexp-alist items like:
;; rackunit check-xxx
("#<path:\\([^>]+\\)> \\([0-9]+\\) \\([0-9]+\\)" 1 2 3)
;;rackunit/text-ui test-suite
("^location:[ ]+\\(\\([^:]+\\):\\([0-9]+\\):\\([0-9]+\\)\\)" 2 3 4 2 1)
And people using other editors can do the equivalent.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
