deft VS jupyter

If, like me, OP is a little slap-dash, happy-go-lucky, can't-decide-what-to-use, lazy, or uncoordinated, https://github.com/jrblevin/deft is a pretty handy package.

For (neo)vim users, there's notational fzf [1], which also requires fzf to be installed [2]. For Emacs, there's Deft [3]. They all what to me are nvalt's core functionality which is fuzzy search into quick note creation/editing. They can also be used in conjunction with nvalt or other markdown based applications since all of them use plaintext. For Deft, you can also choose to create .org files.

[1] https://github.com/Alok/notational-fzf-vim

[2] https://github.com/junegunn/fzf

[3] https://jblevins.org/projects/deft/

Check out Deft.

Take a look at Deft, this is what I use.

You may be looking for deft: https://jblevins.org/projects/deft/

I like deft for this.

Honestly I've been in the same boat as you for ages and have even tried writing my own zettelkasten packages here and there on top of things like deft (I started with zetteldeft, which shows).

Is there an easy way to move a ton of org files into org-roam? I've used just a flat directory of org files that I've searched with the excellent Deft package for years, and I'd like to give org-roam a whirl. Is there an easy way to import all those notes in bulk? (Don't all notes need an ID?)

‘Course, there’s an Emacs command to do that: Deft mode.

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