Pluto Questions

Does Pluto automatically stores files in the cloud on github or something ? . . . just notice it accessing github when I start and load previous files.

Does Pluto assign filenames (seperate from the ones the user save files as) ?
Notice filenames showing up like: “Fascinating experiment.jl”, “Groundbreaking proof.jl”, “Groundbreaking computation.jl”. Not sure where these name came from . . . : /

Is it possible to use more than one Pluto session at a time ?
Notice if I open a second instance of Pluto to do side by side comparisons, the first session gets to a point that it indicates " Not yet authenticated . . . Open the link that was printed in the terminal where you launched Pluto."

Evaluating if I should use Jupyter notebooks or Pluto. It seems that Pluto may have some wizwig stuff that needs to be reckoned with . . .

Hope all is well with Julia users !


No. Notebook files are stored as default in .julia/pluto_notebooks, but any storage location can be used.
The Github access may be due to installation of Julia packages (both the General registry and the vast majority of Julia packages are on Github).

Pluto notebooks have the extension .jl. If a new notebook is created, it gets a default filename because the notebook is saved on any cell execution, but you can change it when manually saving the notebook.

Yes. Ctrl+click on the Pluto symbol in one notebook opens a new tab with the Pluto startup screen, where you can open a 2nd notebook (or create a new one).
Each notebook is run in a separate Julia process.

In principle it should also be possible to run 2 Pluto servers in parallel, but then you need to take care to use the correct secrets for each instance.

Use Pluto (OK, I might be a bit biased :wink: )


Very helpful.

So many choices . . . there is also VS Code and the Julia REPL . . .

: )

There is also GitHub - JuliaPluto/PlutoTest.jl: 🎈 Visual, reactive testing library for Julia. Time machine included. for writing tests in Pluto (alpha version).
This could be combined with either development in VSCode (with Revise) or directly in the Pluto notebook.

On VS Code you can have a notebook like (jupyter like) experience using just the Julia extension. In any .jl file you can divide chunks of codes by using a comment separator starting with ## and running it with a Shift+enter. The julia extension will open a RELP and execute the selected (by cursor position) code section.


# A first section that load stuff
using Example

## -------------------------------- (Note the leading ##)
# A section that just declare a variable
name = "John"

## --------------------------------
# Do stuff

The output is printed in the relp each time you execute a section.

The running section is persistent and does not care about the particular file you are in. You can run pieces of code from different files. And it has, unlike jupyter, a good interaction with version control from the get-go.