From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: Literate config and :tangle clauses Date: Sun, 25 Dec 2016 09:52:52 -0800 Message-ID: References: <87r34yz1wd.fsf@laptoptop.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="0-118219969-1482688372=:1059" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38717) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLCyl-000398-7o for emacs-orgmode@gnu.org; Sun, 25 Dec 2016 12:53:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cLCyg-0005Em-CB for emacs-orgmode@gnu.org; Sun, 25 Dec 2016 12:53:03 -0500 Received: from iport-bcv2-out.ucsd.edu ([132.239.0.73]:6452) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1cLCyf-0005E8-R6 for emacs-orgmode@gnu.org; Sun, 25 Dec 2016 12:52:58 -0500 In-Reply-To: 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: joakim@verona.se Cc: emacs-orgmode@gnu.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-118219969-1482688372=:1059 Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 8BIT On Sun, 25 Dec 2016, joakim@verona.se wrote: > aaermolov@gmail.com writes: > >> Hi all! >> >> Recently I've experienced a kind of a problem - my literate Emacs config >> stopped tangling correctly, only a subset of code blocks were found in >> resulting .el file. >> I've looked at it a bit closer and it seems now (not earlier than 9.0.2) >> the :tangle clause became required. I've searched Org repo but failed to >> find a respective commit or any reference to the relevant info. > I don't think the problem lies with any revision to org. First, what `C-h v org-babel-default-header-args RET' shows below is unchanged for at least a year: --8<---------------cut here---------------start------------->8--- org-babel-default-header-args is a variable defined in ¡ob-core.el¢. Its value is ((:session . "none") (:results . "replace") (:exports . "code") (:cache . "no") (:noweb . "no") (:hlines . "no") (:tangle . "no")) ... --8<---------------cut here---------------end--------------->8--- Note that `(:tangle . "no")' sets the default behavior. Second, I have files that depend on the above. i.e. I set the header on a few blocks to `:tangle yes' and leave the rest alone, relying on the above default to keep them from being tangled. > I also experienced the same behaviour. :tangle became required, which it > wasn't previously. > > My solution was just to add the ":tangle yes" tag everywhere. > > >> >> Can anyone point me to the right direction? >> Use #+PROPERTY: header-args :tangle yes (and type `C-c C-c' to reset the buffer the first time you type it) and review (info "(org) Using header arguments") for tips on how to control the application of header args. HTH, Chuck --0-118219969-1482688372=:1059--