-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use modular components of scimax (like new ipython)? #191
Comments
You can do any of the following:
You will have to read the source files to see what is required, and then debug what is missing. You probably need scimax-ob and scimax-org-babel-ipython-upstream. You do not need scimax-notebook or scimax-org-babel-ipython (which is the old branch). |
These seem to be the minimum needed to get things working for me on a (very) simplified spacemacs install:
My .spacemacs loads a file that adds a few things like Easy Template definitions, keymap tweaks, etc., and the nuke-ipython function (found in scimax-org-babel-ipython.el). Edit: I should mention this assumes
|
This works, thanks. I'll leave it open in case you want to reference it for the docs or anything. |
Thanks. |
I just discovered scimax and I'm pretty excited about it. I'm looking to get started with some of the features, like the fancy new
ob-ipython
.Since I already have a fair amount of emacs/org configuration of my own, I'd like to incorporate scimax a bit at a time, rather than enabling the whole thing all at once, so I have a better sense of what changes I'm making and so I have finer-grained control of which packages are controlling what.
I see the docs say
Is there a recommended way to use only the new
ob-ipython
, while keeping the other components disabled?I already have the MELPA version of ob-ipython installed. Should I then clone this repo and
(require 'scimax-ob)
and(require scimax-org-babel-ipython-upstream)
to get the added scimax ipython features? What ofscimax-ob
,scimax-notebook
andscimax-org-babel-ipython
?Thanks for your help!
The text was updated successfully, but these errors were encountered: