quickrun VS jupyter

Since you are asking, to give an example of a package that has some similar features, I would say "quickrun.el" would be one.

I guess, to start with, it is best to answer for yourself why you would recommend users to use Emacs. Even better if you write it down for yourself, so that you could publish it as a blog post (in org-mode). If they are coding in some particular language, then also explain your optimal workflow for that language. E.g. when you are teaching python, then tell them how to use the inferior-shell and send code to it. Or maybe how to use ipython notebooks or emacs jupyter. Or when coding C, explain how to use Makefile's or quickrun. I guess if you recommend Emacs, you expect them to learn some elisp (I would never recommend users to use Emacs without learning some elisp). Tell them that elisp is more fun than it looks initially, and it isalmost as easy as e.g. python. Possibly show how to use basic magit, and org-mode and definitely tell them about evil and Spacemacs/Doom (or other starter kits). In the end, simply try to motivate your enthusiasm and offer a helping hand. But accept that (some) users have no need/time for it. Then second, use the answers here to improve your 'inspirational talk/writing'...

is it like quickrun? https://github.com/emacsorphanage/quickrun

For ipython, you'd better use some more specialized package like https://github.com/emacs-jupyter/jupyter, not the generic python support.

I have seen this thread, but I don't want to have to put an extra source block to set the renderers in every org file where I use plotly. Does anyone have a good solution for the moment? Any help is appreciated.

Should no one take you up on the bounty, I suggest trying emacs-jupyter instead. I've had better luck with it in the past.

For anybody following along with the examples, a few points/tips that might help newcomers:

1. (By default) before you can use Python source blocks, you need to have the Org Babel Python functionality loaded which is most easily done by evaluating the elisp (require 'ob-babel), but there are other ways also [1].

2. The first example, which uses the print function, will not output anything because the Python blocks by default are evaluated inside a function body and the return value is returned to Org [2]. To return the printed output instead, you need the header argument ":results output". There is an example of this syntax later in TFA.

3. If you are serious about replacing (or complementing) other Jupyter tools with Org mode, you might want to eventually look at emacs-jupyter [3], which provides a more advanced handling of outputs and also supports other (i.e. non-Python) kernels.

Also, I don't think I've ever seen anything like the debugging example and when I tried to replicate it out of curiosity, the block simply failed with a bdb.BdbQuit exception. Am I missing something? What is supposed to happen?

[1] https://orgmode.org/manual/Languages.html

[2] https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-...

[3] https://github.com/nnicandro/emacs-jupyter

Emacs, Sublime Text 3 and Atom Pulsar can all do this with arbitrary Jupyter kernels with the emacs-jupyter/code-cells, helium and hydrogen packages, respectively.

You can use emacs as a jupyter client if that would help in your case https://github.com/nnicandro/emacs-jupyter

I've been using code-cells together with emacs-jupyter, the combination of the two lets you work pretty much identically as you would in Atom with Hydrogen, Sublime with Helium, or VSCode with the Jupyter Python extension; you just delimit code cells with #%% and execute in a separate Jupyter REPL buffer. It does require some getting used to the key bindings though (or some tweaking to make it more similar to what you're used to).

For writing source blocks: https://github.com/nnicandro/emacs-jupyter