Skip to content
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.

Sign up for GitHub

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

Jump to bottom

scel: Directory change of sclang/scsynth in 3.7-beta1 causing error #1860

Closed
dotinspace opened this issue Feb 8, 2016 · 4 comments
Closed

scel: Directory change of sclang/scsynth in 3.7-beta1 causing error #1860

dotinspace opened this issue Feb 8, 2016 · 4 comments
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. good first issue indicates issue tickets that are suitable for a new contributor os: macOS
Milestone
3.7.0

Comments

@dotinspace
Copy link

  • OS X 10.11.3
  • SC 3.7-beta1
  • emacs 24.5 (installed with homebrew)

When trying to run emacs -sclang I get the following error:

/Applications/SuperCollider/SuperCollider.app/Contents/Resources/sclang: No such file or directory
*** SCLang exited abnormally with code 127 ***

Obviously, the folder should be /Applications/SuperCollider/SuperCollider.app/Contents/MacOS and not /Applications/SuperCollider/SuperCollider.app/Contents/Resources for 3.7, but trying to change that setting has no effect at all, and scel still tries to run from the Resources directory.
@crucialfelix crucialfelix added bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. os: macOS env: scel good first issue indicates issue tickets that are suitable for a new contributor labels Feb 10, 2016
@crucialfelix crucialfelix added this to the 3.7.0 milestone Feb 10, 2016
@miguel-negrao
Copy link
Member

Grepping scel directory there aren't any hardcoded paths pointing to something ending in Resources. The readme says:

Customization

To fine-tune the installation from within emacs' graphical customization interface, type:

M-x sclang-customize

In particular, you will have to customize `sclang-runtime-directory'.

So I think you just have to set sclang-runtime-directory correctly. Probably this can be closed ?

@dotinspace
Copy link
Author

Nope. Not working. Settings changed through sclang-customize are not persistent. It resets to .../Resources/sclang. I can run sclang fine after I set program path and runtime directory manually, but would have to do that every time I start emacs. It is of course highly likely that I am doing something wrong. So, I suppose closing it makes sense. More people would have this problem if it was not just me doing something wrong in the setup. Thanks.

@jamshark70
Copy link
Contributor

I haven't used the emacs interface in some time, but as I recall, I always used the M-x customize-group interface for these settings. It would persist them in ~/.emacs.

Maybe check ~/.emacs for stray assignments to the relevant variables? If there are any, it could step on the customize interface's toes.

@dotinspace
Copy link
Author

Thanks for the tip, but ~/.emacs.d/init.el has no conflicting assignments, unfortunately, so customise interface's toes are unscathed. I'll try one more time from scratch and see how it goes.

Update: the problem is with sclang-extensions package, not scel. Sorry about all the fuss!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. good first issue indicates issue tickets that are suitable for a new contributor os: macOS
Projects
None yet
Milestone
3.7.0
Development

No branches or pull requests
4 participants
@crucialfelix @jamshark70 @miguel-negrao @dotinspace