-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Do not run all cells when opening notebook #92
Comments
Thanks for posting these issues! You can disable auto-run by setting a flag before starting the server: julia> using Pluto
julia> Pluto.CONFIG["PLUTO_RUN_NOTEBOOK_ON_LOAD"] = "false"
julia> Pluto.run(1234) This should use |
What you are suggesting is a creative solution, but it means implementing downstream evaluation (and disabling upstream evaluation?) during the first run - this would make the effect of clicking "run cell" ambiguous. Implementing auto-run (and adding an option to disable it) was very intentional. It means that the notebook is reactive right away, instead of all cells starting out in a limbo state of having synchronised code but not yet being part of the reactivity graph. I think the current solution is much more in line with the philosophy of the project - your notebook is a descriptive program, not an imperative one. |
I think I understand what you mean: I should consider a notebook as one whole reactive object which happens to be extendable incrementally cell-wise. It is not a collection of more or less separate cells. The latter is probably what Jupyter is there for. With that in mind I can totally accept the coffee-time forced upon me when a notebook starts :-). |
update: |
The environment variable you mentioned is a 'hidden' feature, and it will be removed soon. I am working on a solution that is much more friendly: |
Pluto.CONFIG["PLUTO_RUN_NOTEBOOK_ON_LOAD"] = "false" Neither of these works for me. what is the updated code? And please disable autorun by default, why is it enabled by the way what use does it have? It is just annoying!! |
For the recent version, looks like the following works: Pluto.run(Pluto.Configuration.from_flat_kwargs(;run_notebook_on_load=false)) More options can be found here: Line 235 in def9d0e
Hope a keyboard shortcut for "execute all cells above" can be added in the future. |
Doesn't work for me now in Julia 1.8.1 and Pluto v0.19.11 |
Doesn't work for me either. Oddly enough it seems to be adding a delay of a few seconds before the notebook is run anyway. |
Interesting, I just checked it again with Julia v1.7.0 and Pluto v0.19.9, and it still works for me. |
I normally launch pluto from a shell alias: Update: Running from the REPL gives the same behavior as |
How about Pluto.jl/src/webserver/WebServer.jl Line 59 in b9158e0
So |
It didn't work, wonder why. I'm using Julia v1.8 and Pluto v0.19.9 |
Is there any update? It also didn't work for me. I am using Julia v1.8 and Pluto v0.19.12 |
Please follow #259 for discussions of this feature. |
The title of the issue does not quite capture what I want, but is a prerequisite for it. Here is what I really want and the use-case for it:
It sometimes happens that I have a really convoluted exploratory notebook where not all cells depend on each other. It further happens that after loading that notebook, that I don't wan't to run all of it but only a certain cell, because I need only that cells output.
If I execute that cell after opening the notebook, would it be possible for Pluto to detect which other cells that cell depends on and only run those? Without having to run all cells once beforehand?
The text was updated successfully, but these errors were encountered: