On Monday, November 9, 2015 at 1:38:56 AM UTC, Matthias Felleisen wrote: > Use drracket. Yeah, I would, but it takes about 30 seconds to start up if I disable all the extensions, add another 10 or 20 for the debugger, and then when I type it lags behind at about 0.25s per character. Also it consumes huge amounts of memory, and that seems to increase without bounds if you leave it open.
> 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. -- 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.
