Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-02-04 Thread Robby Findler
Going back in this thread, I think that changing which files DrRacket compiles is not the right direction to go to solve the problem discussed here. The problem is that planet2 is running raco setup in a strange configuration. Avoiding compiling files will not solve this problem. Robby On Sat,

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-02-04 Thread Jay McCarthy
I'm not sure why it is a strange configuration, but maybe I missed that part of the thread. More generally, why should running the function version of raco setup behave differently in a DrRacket buffer than it does on the command line? Jay On Mon, Feb 4, 2013 at 6:17 AM, Robby Findler

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-02-04 Thread Robby Findler
It isn't to do with drracket. It is to do with the fact that it is triggered in a context where, say, the reader doesn't behave the way it would with the default parameters. Long story short: there are lots and lots of parameters that affect how compilation and raco setup generally behave. If

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-02-04 Thread Matthew Flatt
I agree. More generally, if running a program has the side effect of configuring DrRacket, then maybe it should not be allowed to run within DrRacket. That is, maybe DrRacket should install a security guard that prevents writing to installed collections. Meanwhile, to install packages from

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-02-03 Thread Danny Yoo
On Sun, Feb 3, 2013 at 8:23 PM, Robby Findler ro...@eecs.northwestern.edu wrote: Why do you think it should include so much stuff? I would have said it should include only the directories where we know that collections live. Can those other directories are also potential places where

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-01-16 Thread Robby Findler
It may be possible to change drracket to only set that parameter when it is compiling files, but for now I think you have to disable drracket's auto compilation (in the language dialog's show details section) to develop programs like this. Robby On Wednesday, January 16, 2013, Sam

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-01-16 Thread Robby Findler
The former. And maybe there is a problem with drracket sharing too much with the user program too. Robby On Wednesday, January 16, 2013, Sam Tobin-Hochstadt wrote: Do you mean the automatically populate compiled directories setting, or the online compilation? Sam On Wed, Jan 16, 2013 at

Re: [racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

2013-01-16 Thread Sam Tobin-Hochstadt
On Wed, Jan 16, 2013 at 10:55 AM, Robby Findler ro...@eecs.northwestern.edu wrote: The former. Ok, great. Happily back to using DrRacket. :) And maybe there is a problem with drracket sharing too much with the user program too. Robby On Wednesday, January 16, 2013, Sam Tobin-Hochstadt