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.

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

Resuse binder session across snippets #13

Open
NixBiks opened this issue May 27, 2019 · 3 comments
Open

Resuse binder session across snippets #13

NixBiks opened this issue May 27, 2019 · 3 comments

Comments

@NixBiks
Copy link

NixBiks commented May 27, 2019

Is it possible to use the same binder session for multiple snippets? For some exercises I want to continue on previous solutions.

@ines
Copy link
Owner

ines commented May 27, 2019

Yes, this is the isolateCells setting here, which is true by default (new session for each cell, i.e. code block):

Out-of-the-box, this is a global setting, though, so you have to decide if you want isolated cells for the whole course, or not. It might be possible to just add this as an attribute to <codeblock>, which passes it down to the Juniper component... but I'm not sure, it might have unintended side-effects.

@NixBiks
Copy link
Author

NixBiks commented May 27, 2019

Cool but it doesn't seem to work?

I just did a = 2 in one session and then a was not recognized in another window.

I get Launching Docker container on mybinder.org... each time I run code in a new codeblock which takes ~20 sec. No chance to have it faster?

@hfboyce
Copy link
Contributor

hfboyce commented Mar 2, 2020

Sorry @ines,
I also tried this changing isolateCells: true in src/components/juniper.js and I am still not having follow up cells a retaining the variables in the previous cell's environment.
Is there anywhere I should look to debug this? I think this feature could be really useful especially for importing modules and data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants