-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apps using torchbear interpreter should read torchbear.scl config file from "app-dir" #196
Labels
Comments
naturallymitchell
changed the title
when running a torchbear app in another torchbear app
when running a torchbear app in another torchbear app's dir, don't check current dir's torchbear.scl for init.lua
Jan 2, 2019
Could you provide clarification? |
if you're working on |
naturallymitchell
changed the title
when running a torchbear app in another torchbear app's dir, don't check current dir's torchbear.scl for init.lua
apps using torchbear interpreter shoudl read torchbear.scl config file from "
Jan 12, 2019
naturallymitchell
changed the title
apps using torchbear interpreter shoudl read torchbear.scl config file from "
apps using torchbear interpreter shoudl read torchbear.scl config file from "app-dir"
Jan 12, 2019
naturallymitchell
changed the title
apps using torchbear interpreter shoudl read torchbear.scl config file from "app-dir"
apps using torchbear interpreter should read torchbear.scl config file from "app-dir"
Jan 12, 2019
dariusc93
added a commit
that referenced
this issue
Jan 12, 2019
Since torchbear isnt setting a directory, it will show it is running from whatever directory it is called from and affecting its ability to read things like scl, etc. Related to #196
that commit broke mp, because it needs to run in current_dir |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: