Re: [O] org-babel: insert named source block
Thanks. That works well, but only shows named source blocks in the particular file. Is there a way to make it show library of babel blocks too? Deepak On 11/15/2017 02:56 PM, Berry, Charles wrote: On Nov 15, 2017, at 11:04 AM, Deepak Cherian <dpak.cher...@gmail.com> wrote: Has anyone here managed to configure ivy or helm to show a list of named source blocks that org knows about? I am imagining this workflow: 1. M-x org-babel-insert-named-source-block (imaginary function) 2. List of named source blocks pops up 3. Hit enter and "#+call: name-of-source-block()" is inserted at point. org has its own function for listing named src-blocks. #+BEGIN_SRC emacs-lisp (defun my-insert-named-src-block ( template ) (interactive) (let ((template (or template "#+call: %s()\n")) (src-block (completing-read "Enter src block name[or TAB or ENTER]: " (org-babel-src-block-names (unless (string-equal "" src-block) (insert (format template src-block) #+END_SRC M-x my-insert-named-src-block TAB HTH, Chuck
[O] org-babel: insert named source block
Has anyone here managed to configure ivy or helm to show a list of named source blocks that org knows about? I am imagining this workflow: 1. M-x org-babel-insert-named-source-block (imaginary function) 2. List of named source blocks pops up 3. Hit enter and "#+call: name-of-source-block()" is inserted at point. Thanks, Deepak
[O] bokeh, ob-ipython and org-mode HTML export
I have a blog post up that might be of interest to some of you on this list: http://cherian.net/posts/bokeh-org-mode.html. It looks at ways to embed interactive Javascript plots using bokeh when exporting org files to HTML (bokeh.pydata.org). Feedback and suggestions welcome! Deepak
[O] org-ellipsis after tag is bolded
E.g. * Heading 1 ... * Heading 2 :noexport:... The second ellipsis is bolded because it appears after a ':'. Deepak
[O] ox-html export bug with CUSTOM_ID
This org file (OPTIONS are to keep the exported file clean) - * heading 1 * heading 2 :PROPERTIES: :CUSTOM_ID: my-name :END: exports to --- 1 heading 1 class="section-number-2">2 heading 2 --- The "" for the second heading is unnecessary. Seems to only occur when CUSTOM_ID is set. Deepak