I don't understand why they announced nbterm at such an early stage tbh. When I tried it it was basically non-working.
[1] https://blog.jupyter.org/nbterm-jupyter-notebooks-in-the-ter...
[2] https://github.com/davidbrochart/nbterm
Edit: cool to see another project supporting kitty terminal's graphics protocol. kitty is a great terminal and has a lot of good ideas. Also, nice to see Euporie has a section on related projects that mentions nbterm.
(Edit: VS Code, Spyder, and PyCharm do support them, but they have their own quirks.)
It supports moving the current line/region up/down (e.g., using <M-up> in Python mode that is activated for editing jupyter-python cells on <C-c '>).
I think I might add a simpler shortcut.
There is an important feature Jupyter has that org doesn’t share: collaboration. If everyone I need to collaborate with already uses emacs and org, great—but that’s a pretty big “if,” I and haven’t seen that opportunity in the wild.
On the other hand, jupyter notebooks may have a garbage format (JSON blobs with embedded b64? Ugh!), and the browser-driven UI sucks (IMO, as an ardent emacser), but they’re ubiquitous and the lingua franca for Python data science. Most everyone you meet is familiar with them and can incorporate them into their workflow, and there’s benefit to the direct rendering pipeline to standalone HTML in a conventional format.
There is actually a viable jupyter interface in emacs, EIN [1]. I’ve used it a lot and it works seamlessly, and reduces the pain of using jupyter by letting me edit within emacs. There are also VS Code plugins that enable jupyter development…
Tldr jupyter can be ugly but it’s widespread and that alone makes org mode Babel analysis a nonstarter for collaboration, but at least there are ways to run jupyter within emacs
[1] EIN == Emacs iPython Notebook https://github.com/millejoh/emacs-ipython-notebook
For now, you'd have to change "editing_mode" to "vi" in config.py
TUI =
(Telephone User Interface) The combination of Touch-tone input from the telephone keypad coupled with speech output from the connected voicemail or IVR application. While early speech technology was struggling to recognize voice utterances for voice control and data entry, the ubiquitous Touch-tone keypad was a practical solution. It works with enterprise telephone networks, the PSTN, public payphones and traditional cellphones. Its centerpiece is the standard 12-key keypad and conventions such as using the pound key for "enter," the star key for "up one level" or "escape," and "1" for yes, "2" for no.
Using this abbreviation for new uses can only reduce readability.
https://acronyms.thefreedictionary.com/TUI
Yes, there is a more established term for TUI, yet it’s not what you thought it is. TUI for terminal user interface is not so new and not so obscure as you make it sound (especially in the data science, ipython, Julia, etc. Community).
I think as it‘s an expert Interface the abbreviation is not such a big problem. Yet, I agree it‘s always good to give the full term before using an abbreviation.
Random note: the best way to support keystrokes such as Ctrl-Enter and Shift-Enter in the terminal is CSI-u mode:
http://www.leonerd.org.uk/hacks/fixterms/
It's supported by most terminals by now.
- from IPython (a better, notebook-style Python interpreter shell)
- to IPython notebooks (IPython, but in a browser)
- to Jupyter Notebooks (IPy notebooks, but more backends)
- to Euporie, a text interface to Jupyter notebooks
Of course this does way more than IPython ever did, or even should do. But it's a pretty funny trajectory, everything old is new again.
(Also, clever name! I'd heard of that particular Greek deity from somewhere else, but never knew she had a moon named after her =])
