At Sun, 8 Nov 2015 21:56:04 -0500, Ben Lerner wrote: > > 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?
For errors while a document is constructed, just running racket -l errortrace -t <my scribble file> would work, since a Scribble document is a Racket program. For an error that happens only during rendering, you could use racket -l errortrace -l scribble/run <my scribble files> since the `scribble` program just runs the `scribble/run` module. I'm not sure why it's `scribble/run` instead of just `scribble`, and maybe it's worth adding a `scribble` module as an alias. I'll think about that more, in case there was a reason that I've forgotten. -- 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.
