From: Nathan Neff <nathan.neff@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org babel tangle: Don't export code
Date: Wed, 25 Sep 2019 06:41:58 -0500 [thread overview]
Message-ID: <CAC=HedAoyNc6n33YgAJZvTjmy-YXHMX_fc2MEeMS_Rh4EYcxFQ@mail.gmail.com> (raw)
In-Reply-To: <87k19wyl9a.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Wed, Sep 25, 2019 at 12:54 AM Ken Mankoff <mankoff@gmail.com> wrote:
>
> On 2019-09-25 at 01:07 +02, Tim Cross <theophilusx@gmail.com> 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.
>
>
Wow - sorry guys but this is really hard to understand - also I found that
the following code will
mess up my config - all of my *other* code blocks are *not* "tangled" and
the only code
block which is "tangled" is the one which I issue :tangle yes fo.
#+BEGIN_SRC emacs-lisp :tangle yes
(some emacs lisp here)
#+END_SRC
The documentation is really vague here and I did not expect it. I mean, I
set :tangle no according to
Tim Cross, and that's fine - the code is not tangled. Then I change it to
:tangle yes and then it's the
*only* block which is tangled? How could I get that from the docs here?
https://orgmode.org/manual/Extracting-source-code.html
I'll propose a change to the docs and submit it - I just want to know if
I'm misunderstanding something
about the docs or if others find that the docs could use some rephrasing
(suggestions welcome).
Thanks,
--Nate
[-- Attachment #2: Type: text/html, Size: 2137 bytes --]
prev parent reply other threads:[~2019-09-25 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 21:18 Org babel tangle: Don't export code Nathan Neff
2019-09-24 23:07 ` Tim Cross
2019-09-25 0:46 ` Nathan Neff
2019-09-25 1:19 ` Tim Cross
2019-09-25 1:43 ` Nathan Neff
2019-09-25 5:53 ` Ken Mankoff
2019-09-25 11:41 ` Nathan Neff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=HedAoyNc6n33YgAJZvTjmy-YXHMX_fc2MEeMS_Rh4EYcxFQ@mail.gmail.com' \
--to=nathan.neff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
--cc=theophilusx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).