From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Neff Subject: Re: Org babel tangle: Don't export code Date: Wed, 25 Sep 2019 06:41:58 -0500 Message-ID: References: <87o8z9qony.fsf@gmail.com> <87k19wyl9a.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000de90e105935f1fa5" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:48551) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iD5f9-0005Cm-O3 for emacs-orgmode@gnu.org; Wed, 25 Sep 2019 07:40:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iD5f8-00015e-Ez for emacs-orgmode@gnu.org; Wed, 25 Sep 2019 07:40:51 -0400 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]:42503) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iD5f8-00015K-Ak for emacs-orgmode@gnu.org; Wed, 25 Sep 2019 07:40:50 -0400 Received: by mail-io1-xd32.google.com with SMTP id n197so12886732iod.9 for ; Wed, 25 Sep 2019 04:40:50 -0700 (PDT) In-Reply-To: <87k19wyl9a.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Ken Mankoff Cc: Tim Cross , emacs-orgmode --000000000000de90e105935f1fa5 Content-Type: text/plain; charset="UTF-8" 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 > #+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 --000000000000de90e105935f1fa5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Sep 25, 2019= at 12:54 AM Ken Mankoff <mankoff@g= mail.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

=C2=A0 -k.


Wow - sorry guys but this is really ha= rd 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-li= sp :tangle yes
(some emacs lisp here)
#+END_SRC

The documentation is really vague here and I did not expe= ct it.=C2=A0 I mean, I set :tangle no according to
Tim Cross, and= that's fine - the code is not tangled.=C2=A0 Then I change it to :tang= le yes and then it's the=C2=A0
*only* block which is tangled?= =C2=A0 How could I get that from the docs here?

https://or= gmode.org/manual/Extracting-source-code.html

I'll propose a change to the docs and submit it - I just want to kno= w if I'm misunderstanding something
about the docs or if othe= rs find that the docs could use some rephrasing (suggestions welcome).

Thanks,
--Nate


=C2=A0
--000000000000de90e105935f1fa5--