emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Guido Van Hoecke <guivho@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Bastien <bzg@gnu.org>,
	Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>,
	emacs-orgmode@gnu.org
Subject: Re: org-babel-tangle
Date: Mon, 15 Apr 2013 21:03:07 +0200	[thread overview]
Message-ID: <m2ppxvvcpg.fsf@gmail.com> (raw)
In-Reply-To: <87r4ibg0bf.fsf@gmail.com> (Eric Schulte's message of "Mon, 15 Apr 2013 11:39:48 -0600")

Eric Schulte <schulte.eric@gmail.com> writes:

> Guido Van Hoecke <guivho@gmail.com> writes:
>
>> Hi Bastien,
>>
>> Guido Van Hoecke <guivho@gmail.com> writes:
>>
>>> Hi Bastien
>>>
>>>> You may need to refresh the configuration by hitting C-c C-c on the
>>>> #+PROPERTY line (or on any #+... line).
>>>
>>> Of course, I should have realised this.
>>> After refreshing, the tangle process works as expected.
>>>
>>> Sorry for the noise,
>>
>> I did read the org manual very carefully before my initial post, as well
>> as after successfully applying the solution. I did not find any
>> statement about the need of such a `#+PROPERTY: tangle yes' line, so
>> maybe the manual should mention this? At least it would have avoided the
>> current noise.
>>
>
> The info page on tangling [1], does mention that the default behavior is
> for blocks to not be tangled.
>
> ,----
> | ':tangle no'
> |      The default.  The code block is not included in the tangled output.
> `----
>
> Could you suggest a note which we could add to that page to improve
> clarity and help others avoid the same trap you fell into?
>

Further reading / study of the manual showed that the required info is
present at the end of section `14.1  Structure of code blocks':

,----
| <header arguments>
| 
| Optional header arguments control many aspects of evaluation,
| export and tangling of code blocks (see Header arguments).
| Header arguments can also be set on a per-buffer or per-subtree
| basis using properties.
`----

And section `14.8.1 Using header arguments' is very explicit and gives
examples of all possible usages.

So the manual is very complete and only needs to be read :P

Again, sorry for the noise.

Respectfully,


Guido

--
He who hesitates is a damned fool.
		-- Mae West

      reply	other threads:[~2013-04-15 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 14:56 org-babel-tangle Guido Van Hoecke
2013-04-15 15:04 ` org-babel-tangle Sebastien Vauban
2013-04-15 15:54   ` org-babel-tangle Guido Van Hoecke
2013-04-15 15:56     ` org-babel-tangle Bastien
2013-04-15 16:08       ` org-babel-tangle Guido Van Hoecke
2013-04-15 16:21         ` org-babel-tangle Guido Van Hoecke
2013-04-15 17:39           ` org-babel-tangle Eric Schulte
2013-04-15 19:03             ` Guido Van Hoecke [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=m2ppxvvcpg.fsf@gmail.com \
    --to=guivho@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --cc=wxhgmqzgwmuf@spammotel.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).