This is some really great advice! Thanks!

I'm still confused about why making an executable isn't working. Am I doing 
something wrong?
Even if I choose the framework option for *this* project (it seems like a 
really helpful thing) 
I'd like to be able to distribute, for example, `.app` "executables" to 
MacOS users who
just want stock configuration, etc...
The existence of an `.app` executables is helpful in other ways, as well. 
For example,
starting an application at startup, icons, etc...

On Monday, May 7, 2018 at 11:16:32 AM UTC-4, Neil Van Dyke wrote:
> Regarding overriding globals, a Racket `parameter` is more idiomatic: 
> And/or, you could load your config file as a module, like `info.rkt` is. 
> You might find `dynamic-require` and friends interesting: 
> For one different way to think about config files, especially if your 
> users are programmers, perhaps your application program could be a 
> framework, and the config file is the program that the user runs, and 
> that config file program instantiates the framework: 

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 
For more options, visit

Reply via email to