emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: tangle and comments.
Date: Tue, 31 Oct 2017 17:42:11 +0200	[thread overview]
Message-ID: <874lqfe33g.fsf@mat.ucm.es> (raw)
In-Reply-To: 877evbbvyb.fsf@delle7240.chemeng.ucl.ac.uk


    > On Monday, 30 Oct 2017 at 19:08, Uwe Brauer wrote:

    > You don't way what version of org you are using but I am assuming a
    > relatively recent version (given your emails in recent past).  In this
Right I am using GNU emacs 26.5 and a very recent compiled git clone


    > case, the comments directive is a src block header argument so should
    > either be on the src line or as a header-args property:


    > So either

    > #+begin_src emacs-lisp :comments org

    > or

    > :PROPERTIES:
    > :header-args: :comments org
    > :END:

Thanks but the following file does not work neither
that is running  org-babel-tangle gives me

Tangled 0 code blocks from tangle2.org
**** tangling with yes or link comments
:PROPERTIES:
:header-args: :comments org
:END:


The top block
#+begin_src emacs-lisp :comments org
  (message "first block")
#+end_src

here's some text which won't be tangled

***** subheading
another block
| 1 | first  |
| 2 | second |
#+source: tangle-el-the-second
#+begin_src emacs-lisp
  (message "second")
#+end_src

and finally a block with a =:noweb= header argument
#+begin_src emacs-lisp :noweb yes
  (progn
    <<tangle-el-the-second>>)
#+end_src

next prev parent reply	other threads:[~2017-10-31 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 17:08 tangle and comments Uwe Brauer
2017-10-31  7:47 ` Eric S Fraga
2017-10-31 15:42   ` Uwe Brauer [this message]
2017-10-31 17:42     ` Yury G. Kudryashov
2017-10-31 18:12       ` Uwe Brauer
2017-10-31 18:24         ` Nicolas Goaziou

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=874lqfe33g.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \
    /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

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).