Very cool to see this – but will only be successful with great terminal plotting tools. The ones the author mentions like the matplotlib interface clearly won't do[0] due to lack of resolution<p>A perfect use case for unicode plotting [1] (shameless plug)<p>[0] <a href="https://github.com/domitry/matascii" rel="nofollow">https://github.com/domitry/matascii</a><p>[1] <a href="https://github.com/olavolav/uniplot" rel="nofollow">https://github.com/olavolav/uniplot</a>
Slightly tangent, but has anyone figured out a good solution for version controlling jupyter notebooks?<p>The closest thing that we've found has been to use the notebook percent format in a simple .py file [0][1]. It plays with git much nicer than an .ipynb and it is still interactive enough for rapid prototyping. However, it would be nice to have some first-class support from Jupyter on this.<p>[0] <a href="https://jupytext.readthedocs.io/en/latest/formats.html?highlight=cell%20syntax#the-percent-format" rel="nofollow">https://jupytext.readthedocs.io/en/latest/formats.html?highl...</a><p>[1] <a href="https://code.visualstudio.com/docs/python/jupyter-support-py" rel="nofollow">https://code.visualstudio.com/docs/python/jupyter-support-py</a>
There is also Emacs Jupyter if you use Emacs, and all sorts of `org-babel` integrations if you use org-mode.<p><a href="https://github.com/nnicandro/emacs-jupyter" rel="nofollow">https://github.com/nnicandro/emacs-jupyter</a>
If you use vim, you can also try <a href="https://github.com/hanschen/vim-ipython-cell" rel="nofollow">https://github.com/hanschen/vim-ipython-cell</a> . It works quite well<p>If you use emacs, ein is also a good choice: <a href="https://github.com/millejoh/emacs-ipython-notebook" rel="nofollow">https://github.com/millejoh/emacs-ipython-notebook</a>
Ok, I failed in basic usage:
Entering nbterm, I assumed some standard key bindings -- None seemed to work. Neither Ctrl-C, Ctrl-D, Ctrl-x ctrl-c, escape q, escape :q, ... seems to work.
So off to google:
Escape Ctrl-q should work. But does not.<p>Ok I'm stuck, let's at least get 1+1 to work.
So entering 1+1 and .. hitting Enter? Shift Enter? No.
Ok, command mode, Ctrl E.. aaaaand it's stuck.<p>Looks nice but I just don't seem to get it to work using anaconda on macos..
The web interface was the main reason I never really used the tool for more than a few test runs. Writing code in the browser combines bad usability and performance with a lack of useful dev tools.<p>Which brings me to the question whether I can edit the code in a text editor as well or I have to write it as shown in the animation. It would be really helpful if there was a shortcut to open the current (code) section in $EDITOR, kind of like Git and other tools do it.
I found that this is almost completely non-working. Ctrl+q doesn't quit, cells don't run. Does it work for others?<p>It also unfortunately uses shortcuts that are native on Mac (ctrl+up and down do "mission control" things).
Would be interesting to spin this into a normal bash terminal where you can edit text in the “cell” like in GUI editor and then execute the cell at the end
VS Code has been making progress to support Jupyter notebooks (<a href="https://code.visualstudio.com/docs/python/jupyter-support" rel="nofollow">https://code.visualstudio.com/docs/python/jupyter-support</a>), but it's not quite there yet. Code completion works, but other features such as user snippets are missing, and it can be quite laggy. Apparently that's because the VS Code team has to reimplement a lot of stuff for Jupyter specifically (compared to adding support for Rust or Go with a language server).
My team is doing a lot of cli-based hacking on notebooks. They’re an interesting developing format.<p>I would love early HN feedback on Notebook Ninja, which is (pre-)alpha here: <a href="https://notebook.ninja" rel="nofollow">https://notebook.ninja</a>