On Wed, Sep 25, 2019 at 12:54 AM Ken Mankoff wrote:
>
> On 2019-09-25 at 01:07 +02, Tim Cross wrote...
> > I just put :tangle no in the block header e.g.
> >
> > #+begin_src emacs-lisp :tangle no
> >
> > #+end_src
>
> Also,
>
> * COMMENT Section
> #+BEGIN_SRC
> # not exported because of COMMENT
On 2019-09-25 at 01:07 +02, Tim Cross wrote...
> I just put :tangle no in the block header e.g.
>
> #+begin_src emacs-lisp :tangle no
>
> #+end_src
Also,
* COMMENT Section
#+BEGIN_SRC
# not exported because of COMMENT
#+END_SRC
-k.
On Tue, Sep 24, 2019 at 8:19 PM Tim Cross wrote:
>
> There are two different concepts - tangling and exporting. When you
> tangle the file, code blocks are written out into code files (possibly
> with evaluation etc). This is part of the 'literate programming' support
> within org.
>
Yep - thank
There are two different concepts - tangling and exporting. When you
tangle the file, code blocks are written out into code files (possibly
with evaluation etc). This is part of the 'literate programming' support
within org.
When you export a file, you are exporting the file
contents into a diffe
Thanks Tim - I wanted to ask the list -- what does "
By default, Org does not tangle the ‘src’ code block on export." mean in
this web page:https://orgmode.org/manual/Extracting-source-code.html
I mean, I have all of my begin_src emacs-lisp blocks with no explicit
:tangle yesand they all are expor
I just put :tangle no in the block header e.g.
#+begin_src emacs-lisp :tangle no
#+end_src
This is how I turn off or remove blocks from my .emacs.d/init.el file,
which is tangled from an or file. You can also put a filename. This is
what I do for Emacs 27, which introduces the early-init.el fi
Hello all,
I use *.org files to configure my emacs and use org-babel-load-file
to configure my org-mode using *.org files. Love the feature.
However sometimes I'm experimenting with code blocks, and want to simply
"turn off" certain code blocks in my *.org files from being executed.
Every time
I