On 09/26/2013 11:02 PM, Atte wrote:

I think it's a bug, though...

...or maybe it's just the "Current directory" setting that's getting in the way. IMHO miniAudicle should consider the directory from where it was called (from command line) "current". The "Current directory" makes sense if someone is opening miniAudicle from a menu, but not really (to me at least) if it's started from a terminal. Regards -- Atte http://atte.dk http://modlys.dk

Hello Spencer, Sorry this is a bigger question than just this particular issue, but can or should we start using the issue tracker at https://github.com/spencersalazar/chuck or elsewhere for tracking these things? I noticed a few smaller issues being tracked there and am curious if I should load it up with all of my language feature requests. :) Thanks, michael On Thu, Sep 26, 2013 at 4:43 PM, Spencer Salazar wrote:

Hi Atte,

Thanks for reporting in. This looks pretty clearly like a bug, but it looks easy to fix. You're correct that miniAudicle should use the current directory of the calling command when opening files from the command line.

Ill post again once an update is available.

spencer

On Thu, Sep 26, 2013 at 2:35 PM, Atte wrote:

...

On 09/26/2013 11:02 PM, Atte wrote:

...

I think it's a bug, though...

...or maybe it's just the "Current directory" setting that's getting in the way. IMHO miniAudicle should consider the directory from where it was called (from command line) "current". The "Current directory" makes sense if someone is opening miniAudicle from a menu, but not really (to me at least) if it's started from a terminal.

Regards

-- Atte

http://atte.dk http://modlys.dk _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Hey guys, Ive been using the GitHub issue tracker for both ChucK and miniAudicle. I think its fine to use either the issue tracker or the mailing list for reports like these, using your best judgment as to which-- for potentially widespread issues or general discussion, chuck-users seems more appropriate, while specific concerns or cut-and-dry bug reports might better be directed to the issue trackers. For better or for worse, posts to the mailing list are disseminated to the general chuck community, so you may get a response quicker from users who have experienced the same issue rather than just me/the ChucK team. Keep in mind also that there are two issue trackers, for both miniAudicle and chuck proper: chuck: https://github.com/spencersalazar/chuck/issues mini: https://github.com/ccrma/miniAudicle/issues ALSO note that the chuck repository is currently under my personal GitHub account, as the official ChucK source repository is an SVN repo hosted here at CCRMA. When we get around to migrating ChucK to GitHub, Im not sure if we would also be able to easily transfer the issue tracker database at the same time. So theres some volatility there. spencer On Thu, Sep 26, 2013 at 11:21 PM, Atte wrote:

On 09/26/2013 11:53 PM, Michael Heuer wrote:

...

Hello Spencer,

Sorry this is a bigger question than just this particular issue, but can or should we start using the issue tracker at

https://github.com/**spencersalazar/chuckhttps://github.com/spencersalazar/chuck

or elsewhere for tracking these things? I noticed a few smaller issues being tracked there and am curious if I should load it up with all of my language feature requests. :)

I posted it here because README.txt says:

"For questions, support, documentation, example code, feature requests, and bug reports, please visit the miniAudicle website (http://audicle.cs.princeton.**edu/mini/http://audicle.cs.princeton.edu/mini/), the ChucK website (http://chuck.cs.princeton.**edu/ http://chuck.cs.princeton.edu/), join the ChucK users mailing list at http://lists.cs.princeton.edu/**, or email the authors at ssalazar@cs.princeton.edu."

Regards -- Atte

http://atte.dk http://modlys.dk ______________________________**_________________ chuck-users mailing list chuck-users@lists.cs.**princeton.edu https://lists.cs.princeton.**edu/mailman/listinfo/chuck-**usershttps://lists.cs.princeton.edu/mailman/listinfo/chuck-users