emacs-ipython-notebook VS crafted-emacs

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

Keep an eye on Crafted Emacs which has a v2Beta release branch. It's been evolving. The v2Beta is a rewrite. It aims to provide a minimalist leg up on vanilla Emacs for new Emacs users. It's goal is to take you from first steps to a point where you have learned a great deal and built your configuration. Then you may be comfortable ditching the Crafted Emacs boilerplate configuration entirely. Think of it as a starter kit. Follow SystemCrafters on YouTube (live stream mostly) & Matrix (they are leaving Discord). Despite the live stream being lengthy, there is much to be learned as you bear witness to David figuring things out. Over time, you pickup on those techniques such as looking up a variable state, reviewing functions, evaluating snippets of Elisp in real time, etc. Also recommend, Mastering Emacs as a fantastic ebook with free updates. Once 29.1 ships, no doubt, there will be a free update to the ebook.

I'd recommend you have a look at crafted-emacs. It's an example of how far Emacs can actually go without third-party packages. Then you can add minimal packages (completion and specific tool integrations) to further enhance the experience.

For me it's quite stable except some issues I had with vertico. Anyways, I first started to rewrite my doom config into plain vanilla emacs (with org mode literate configs), and then I discovered crafted which allowed me to remove some code with commonly set sane defaults, e.g. stuff from https://github.com/SystemCrafters/crafted-emacs/blob/master/modules/crafted-defaults.el.

I have been surprised at how many people have so ardently defended only using built-ins and raw package.el and their own janky ensure methods when use-package was available and did it all better. And, it even lets you configure Emacs itself (not just packages), as well as seamlessly letting you try different package management tools like straight.el. Getting it into Emacs itself hopefully makes this a more prevalent way of showing users how to craft their own config.

If you need a staring point for configuring there's some nice light ones like emacs-bedrock and crafted-emacs, and also some fully pre-configured Emacs distributions that you can choose from (though those look harder to configure to one's personal needs to me, but I haven't tried them so wouldn't know).

I'll second https://github.com/SystemCrafters/crafted-emacs

And if you find yourself between the two extremes, perhaps https://github.com/SystemCrafters/crafted-emacs