Jumping between terminal and IPyNB is confusing people

[chrysn]

Many questions in today's tutorials related to people not quite getting what needs to be executed in a terminal, vs. what can be run directly in the ipynb. Could we unify to one side? AIU IPython does support longer-running commands (or commands that send more output over time), so it should be possible to do everything in there.

[aabadie]

On more complex scenarios (e.g having multiple terminals running in parallel) this is hardly possible. There's no perfect solution and we (with the IoT-LAB team) decided that the current solution was the less painful.

There's a Jupyter Notebook dedicated to basic Jupyter usage (getting-started.ipynb) that explains when i) to use the regular executable cells (ctrl+enter) and what to do with raw cells (open a separate terminal, run commands there).

Using Jupyerlab is also convienent to edit the Makefile/C files directly in the browser. That is not possible using just Jupyter Notebooks.