castlemacs VS emacs-ipython-notebook

I started my Emacs journey with Spacemacs but it wasn't good since it's not actually Emacs - you need to learn entirely new stuff on top of Emacs stuff. In the end I gave up and settled with IntelliJ IDEA for Scala development. In five years I returned to Emacs, but started from very simple Castlemacs distribution, learning the meaning of each line, copying to my config only settings I needed, mostly related to configuring Emacs to behave properly on macOS. I don't bother with Doom Emacs, my startup time of 3 seconds doesn't bother me.

I started from this https://github.com/freetonik/castlemacs, it's not been updated for a few years, but a good starting point if you're on macOS.

https://github.com/freetonik/castlemacs is the approach where I finally understood and was the missing tutorial for mac users. I've done the emacs embedded tutorial, but got stuck at that weird usage of ESC key as Meta key. That repo laid down the bridgework to me being comfortable with emacs. Still very sparse, but getting there!

Lower the barrier to entry, maybe give them your configuration or some sort of starter-kit, I think castlemacs is good choice as it is quite simple and useable. Tell them to fork it on Github and use it.

I think IJKL keys are probably better then arrow keys, see how castlemacs does it.

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.)