Closed LFSaw closed 10 years ago
Thanks ! It was a bad regex in the interpreter. Fixed, but I have to do a new atom-supercollider release before you will see the update.
yay! will test as soon as i am allowed :)
i'll also have a look if i'm able to directly get the package from github without going throug the package manager... makes testing (and maybe fixing) easier.
there's a few steps. I should document it so that people can contribute.
clone https://github.com/crucialfelix/supercolliderjs
learn about https://www.npmjs.org/doc/cli/npm-link.html this will link the cloned copy of supercolliderjs so that your atom-supercollider uses that instead of checking out its own copy
then the atom-supercollider source that I work with is directly inside ~/.atom/packages/atom-supercollider
but its probably better to do this:
https://atom.io/docs/v0.144.0/contributing-to-packages
because you will want to have your own github fork and link that copy into atom.
then make a test project just for doing development and open that in development mode.
use https://atom.io/packages/project-manager and set that test project to always open in development mode.
do "Window: reload" to get any changes and restart.
On Sun, Nov 9, 2014 at 10:42 AM, LFSaw notifications@github.com wrote:
i'll also have a look if i'm able to directly get the package from github without going throug the package manager... makes testing (and maybe fixing) easier.
— Reply to this email directly or view it on GitHub https://github.com/crucialfelix/atom-supercollider/issues/25#issuecomment-62297436 .
sorry to push this again, but as I am currently not able to make the complex steps but rather qould like to test the amazing features of the environment, would it be possible for you, @crucialfelix, to do a new atom-supercollider release that integrates that fix?
thanks!
done !
apm publish patch Preparing and tagging a new version ✓ Pushing v0.3.5 tag ✓ Publishing supercollider@v0.3.5 ✓
On Sun, Nov 16, 2014 at 1:32 PM, LFSaw notifications@github.com wrote:
sorry to push this again, but as I am currently not able to make the complex steps but rather qould like to test the amazing features of the environment, would it be possible for you, @crucialfelix https://github.com/crucialfelix, to do a new atom-supercollider release that integrates that fix?
thanks!
— Reply to this email directly or view it on GitHub https://github.com/crucialfelix/atom-supercollider/issues/25#issuecomment-63217445 .
thanks so much! I'll check it out ASAP! (I like that squirrel...) edit: the bug is fixed, now for some real-life experiments :)
Hey Felix,
first of all nice editor addition, love it!
here is something weird: Evaluation
???