[chuck-dev] chuck-dev Digest, Vol 65, Issue 2

Kassen signal.automatique at gmail.com
Sat Jan 5 18:39:33 EST 2013

On Sat, Jan 05, 2013 at 03:16:56PM -0800, Spencer Salazar wrote:
>    Hey Casper,
>    Automatically executing .ck files at startup works in the current release
>    version of chuck. It was introduced as a way of allowing "chugins" that
>    were written purely in ChucK code.*
>    spencer

Just thinking out loud here, fire at will and shoot holes.

Would it make sense to include a "~.chuckrc" in the list of such files
(with a matching kind of thing for Windows)?

I also imagine that such a file might use a 


Type namespace, reserved for files run as the VM starts. Here "foo"
would be things that would ordinarily be commandline flags like;



This would remove the need for scripts to start the VM in different
ways for different patches and .chuckrc would set defaults, for
example to deal with the case where we would use multiple soundcards.

The mini has such settings, ChucK doesn't, I imagine they'd share the
same file.

Note that caution-to-the-wind would require a y/[n] dialogue to
prevent the theoretical risk of a ChucK virus flattening a Computer
Music lab.

I think this would probably be quite practical, but I also imagine it
could have huge repercussions. I'm not proposing it so much as I'm
inviting critique.

Fire at will :-)

More information about the chuck-dev mailing list