Is there any chance this is related to using pretty-print-hook and
pretty-print-size-hook?
https://github.com/racket/drracket/commit/89df6b8cca0f862e52d22db1da733524ebf95d80
That change is very recent; maybe more recent than what John is using.
--
You received this message because you are su
> On Apr 30, 2015, at 7:07 AM, Robby Findler
> wrote:
>
> Okay, I've pushed a fix for this.
>
> Thanks very much for the report!
Fantastic! I’m amazed you were able to extract anything from my vague report.
John
--
You received this message because you are subscribed to the Google Groups
Okay, I've pushed a fix for this.
Thanks very much for the report!
Robby
On Tue, Apr 28, 2015 at 2:04 PM, 'John Clements' via dev-redirect
wrote:
> This is probably not reproducible, but I’ve noticed that DrRacket has been
> behaving differently recently when printing even moderately large qua
I don't think so. I did manage to reproduce it and I understand why it
goes wrong and am thinking about how to fix it. Hopefully I'll find
some time later today to focus on it.
Robby
On Wed, Apr 29, 2015 at 11:16 AM, Greg Hendershott
wrote:
> Is there any chance this is related to using pretty-p
I don't think anything has been fixed related to this since April
12th. My simple attempt (below) didn't provoke bad behavior, either.
And the last change to the io bits of DrRacket was back in December
(PR 14871, if you recall :).
Robby
#lang racket
(for ([x (in-range 1000)])
(display (make-st
This is probably not reproducible, but I’ve noticed that DrRacket has been
behaving differently recently when printing even moderately large quantities of
output; lots of GC pauses, most notably.
Today, I hit -k while waiting, and got DrRacket into a bad state where it
wasn’t responding to keys
