castlemacs VS jupyter

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.

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