At Wed, 06 Apr 2016 11:56:51 -0400, "John Clements" wrote: > > > On Apr 6, 2016, at 7:35 AM, Matthew Flatt <[email protected]> wrote: > > > > I haven't been able to replicate the problem, so far, even though my > > machine and installation is similar to yours. > > > > Do you have a Racket installation on a different machine that you can > > check? Whatever the problem is, my guess is that it's specific to OS X > > (but that's just a guess). > > > > Does it matter whether you run the program in DrRacket or just through > > `racket`? > > I’m able to successfully replicate the problem on my machine at work. > However, the problem does seem to be specific to DrRacket. > Furthermore, I find that *restarting* DrRacket appears to solve the > problem. > > If this workaround continues to work, then I suppose I won’t fret, > though it’s a bit worrisome. > > I’ll file a bug report if I find that this becomes reproducible. Apologies > for not trying to restart DrRacket earlier; I suppose this can be seen as a > tribute to my belief in its stability?
If the problem happens after DrRacket has been running for a while, then that's good information and definitely a problem to investigate. Thanks! -- 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.
