Julian Rohrhuber

Well, we do have: ``` var a, b, c; #a, b ... c = {1.rand}!10; ``` So it would be the closest to have: ``` var #a, b ... c...

Yes, I also think that the default should be the file a function or routine was defined in. But we could keep this in a separate pull request? The current...

> > Yes, I also think that the default should be the file a function or routine was defined in. > > Sorry, the default of what? The default for...

Well, I think that `resolveRelative` should always resolve to the current `filenameSymbol` instead of to `nowExecutingPath`. We have two possibilities: 1. either we call `resolveRelative` in some text file directly...

I think we don't have to change the interface. When you call `"my/path/to.scd".resolveRelative`, you are inside a function def, and that can be used in the implementation of `resolveRelative`. If...

> So you're suggesting the use of `getBackTrace`? I tried this but couldn't get it to work. I'll have another look though. Both one and two can use this mechanism...

Ah yes, this is true. In any case, the current implementation should be able to correctly do this after this adjustment: ```supercollider resolveRelative { var path, caller; caller = thisMethod.getBackTrace.caller.functionDef;...

> I'm not a fan of this implementation. It will fall back to the executing path if used in a quark or class lib. It does look hacky, but it...

> I can't get it to work properly with nested files Adding your above tweak to `resolveRelative`. > This final line should print `"..../dir/nested/c.scd"`, but I'm getting `"/home/jordan/.repo/SuperCollider/SCClassLibrary/Common/Core/d.scd"`. Well, I...

Hm strange. Just for precision. 1. save a file named "sc-test.scd" on the desktop with the following as content: ```supercollider "outside of a function, the full path is: '%'".format("".resolveRelative).postln; AppClock.sched(0.3,...