Re: [chuck-users] miniAudicle doesn't open files supplied as command line arguments

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