On 11/8/2015 9:18 PM, Nota Poin wrote:
Or if you insist on command line usage, use error trace.
What's wrong with command line usage? Anyway, I was going to say this:

http://docs.racket-lang.org/errortrace/using-errortrace.html

That seems to enable stack traces that work.

Relatedly, is there a way to use this stacktrace mechanism with scribble? That is, can I write `scribble -l errortrace <my scribble files>` or `racket -l errortrace <however you invoke scribble manually> <my scribble files>`, or would that not work out for some reason?

--
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 racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to