quickrun VS emacs-ipython-notebook

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

the github source : https://github.com/millejoh/emacs-ipython-notebook

I used https://github.com/millejoh/emacs-ipython-notebook at one employer and it works quite well for Jupyter. Of course Org is great but if your coworkers are unfamiliar it's probably a non-starter.

Looking at https://github.com/millejoh/emacs-ipython-notebook/issues this person seems to be using the github issues tracker as a combination of their personal tech support line + ranting board.

Maybe Emacs should have went down the road to have good Jupyter notebooks support instead, even EIN's maintainer was advising against using notebooks.

So that project was forked and this is the better location https://millejoh.github.io/emacs-ipython-notebook/

Except when it doesn't work. I tried using it a few months ago on both Windows and WSL, but I had to give up. Surprisingly, EIN¹ running a Maxima kernel worked.

I was going to try again before commenting, but I broke my WSL setup last week and didn't have time to fix it yet, but I sure will try it again next month.

¹ http://millejoh.github.io/emacs-ipython-notebook/

EIN also looks good but I haven't used it.

From my perspective when I had to turn ML models from a "real scientist" to something I could use in production, emacs-ipython-notebooks[1] was immensely helpful for me, since it allowed to connect to the jupyter server and edit and copy things from emacs to other code places as if I'm looking at an org mode file.

I see the appeal of Jupyter notebooks for someone testing out things or experimenting, but it's a bit like a brain dump that isn't that trivial to navigate around when a second or third person is involved.

[1] https://github.com/millejoh/emacs-ipython-notebook

Hey all! I'm quite attracted by the Emacs IPython Notebook (ein) package and would love to incorporate it into my workflow. However last time I tried (about a year and a half ago) it was officially unsupported in spacemacs and my experiments led to constant headaches like undotree failing, notebooks not saving, native compilation crashing, and a reliance on elpy for IDE features (afaik the only elpy layer available can be found here, uses ESS bindings, and seems to be orphaned.)