Re: [racket] Places acting differently in DrRacket and Racket

It looks like that was the problem. Thanks! However, if I add (place-wait p) after defining p as the place, DrRacket runs out of memory (and never prints anything), while Racket gives a "place: scheduler pipe failed" error and runs the place body about 50 times. Anything else obvious I'm missing?

Re: [racket] Places acting differently in DrRacket and Racket

Does your racket program exit before the place runs? Robby On Wed, Oct 17, 2012 at 11:12 PM, Nick Shelley wrote: > It's usually the case that I'm just missing something obvious, but when I > have a file that just creates a place that prints something and I run it in > DrRacket, I see the thing p

[racket] Places acting differently in DrRacket and Racket

It's usually the case that I'm just missing something obvious, but when I have a file that just creates a place that prints something and I run it in DrRacket, I see the thing printed after a slight pause, but when I run the file with the racket executable from the command line, I don't see anythin

[racket] Hackathon results

Hi all, In case you didn't already see it, the Hackathon wiki page has been updated with a "Results" section showing all the hacking that got done during the event: https://github.com/plt/racket/wiki/RacketCon-Hackathon-2012 (scroll to the bottom) If there's anything missing, feel free to add

Re: [racket] Keyboard key state

Thank you very much Danny. That may have been a good near-solution, but unfortunately keystrokes like NumLock, CapsLock and friends are not caught by the event handler (CapsLock is caught, though, but not as a standalone event), at least on my machine(s). Also, in fact, I wanted among other things