From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guido Van Hoecke Subject: Re: org-babel-tangle Date: Mon, 15 Apr 2013 21:03:07 +0200 Message-ID: References: <86ehebesyl.fsf@somewhere.org> <87txn76b50.fsf@bzg.ath.cx> <87r4ibg0bf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47701) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URogO-0006Jf-Cc for emacs-orgmode@gnu.org; Mon, 15 Apr 2013 15:03:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URogK-0001gb-3b for emacs-orgmode@gnu.org; Mon, 15 Apr 2013 15:03:16 -0400 In-Reply-To: <87r4ibg0bf.fsf@gmail.com> (Eric Schulte's message of "Mon, 15 Apr 2013 11:39:48 -0600") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: Bastien , Sebastien Vauban , emacs-orgmode@gnu.org Eric Schulte writes: > Guido Van Hoecke writes: > >> Hi Bastien, >> >> Guido Van Hoecke 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': ,---- |
| | 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