Hi Salomon,
Babel definitions, in this case, lots of elsip blocks to add behaviors like
this example to clear bloc results on save to avoid polluting commits that
can be turned on and off per section with properties.
#+name: Clear-Results-On-Save
#+begin_src emacs-lisp :results none
;;; code to cl
Hey Doug,
What types of things are in GeneralORGTools.org? Are those babel
definitions? Or something else?
-s-
On Tue, Jun 16, 2020 at 11:21 AM Salomon Turgman wrote:
> Thanks for the useful example. I will take a look. Didn't know about
> org-sbe!
>
> -s-
>
> On Mon, 15 Jun 2020 15:52:16 -040
Thanks for the useful example. I will take a look. Didn't know about org-sbe!
-s-
On Mon, 15 Jun 2020 15:52:16 -0400
Douglas Perrin wrote:
> Hi Salomon Turgman,
> I do this a lot and have had success using a combination of #+SETUPFILE to
> bring in names and configuration, and org-sbe to do ini
Hi Salomon Turgman,
I do this a lot and have had success using a combination of #+SETUPFILE to
bring in names and configuration, and org-sbe to do initialization. I mix
emacs vars and org names in my source headers with back quoting.
The following example has a template file containing user/local
Hello,
Salomon Turgman writes:
> Now, if I include the definition in every org file that I want to use it,
> everything works well. However, if I include the definition in a central
> org file that I import using #+SETUPFILE, things break and I don't get the
> proper output in my html exports.
Hello all,
I have created what I hoped was a reusable org-babel snippet that looks
like this:
#+NAME: simulation
#+HEADER: :var cap="DEFAULTCAPTION" :cache yes :eval no-export :var
altimage="1_image.svg#img1"
#+BEGIN_SRC emacs-lisp :var divid="defid" :var num=1 :results html :exports
results
(for
