Re: Org babel tangle: Don't export code

[Tim Cross <theophilusx@gmail.com>]

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 file i.e.

#+begin_src emacs-lisp :tangle early-init.el

#+end_src

#+begin_src emacs-lisp :tangle init.el

#+end_src

Nathan Neff <nathan.neff@gmail.com> writes:

> 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 go to do this, I search the web for 30-60 minutes and I'm frustrated and
> confused by
> the myriad options and documentation.
>
> All I want to do is mark a source code block in my *.org files so that the
> particular code block is:
>
> 1) Not exported to the resulting .el file when tangling
> Or
> 2) Not ran in the resulting .el files when tangling
>
> I recently spent 30 minutes to an hour trying to figure out how to simply
> "disable" or "prevent" or "exclude" or "quit" or "don't" or "stop" or
> "please don't do this"
> to a code block in my *.org files.  I don't want to mark the code block as
> "text", unless there's really no other option.
>
> In my opinion, the documentation does not simply define how to do this
> relatively common task.
>
> Can someone please point me in the right direction?  Also I would be
> willing to submit a doc-fix or FAQ item if there is currently not an item
> to do so.  I'm lost and do not want to spend more time on this seemingly
> easy task.
>
> Thanks,
> --Nate


-- 
Tim Cross