From mboxrd@z Thu Jan 1 00:00:00 1970 From: aaermolov@gmail.com Subject: Re: Literate config and :tangle clauses Date: Mon, 26 Dec 2016 11:49:50 +0300 Message-ID: <87y3z3krbl.fsf@laptoptop.i-did-not-set--mail-host-address--so-tickle-me> References: <87r34yz1wd.fsf@laptoptop.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35883) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLQyj-00077c-Oi for emacs-orgmode@gnu.org; Mon, 26 Dec 2016 03:49:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cLQyg-00065z-OV for emacs-orgmode@gnu.org; Mon, 26 Dec 2016 03:49:57 -0500 Received: from mail-lf0-x242.google.com ([2a00:1450:4010:c07::242]:35260) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cLQyg-00065l-GI for emacs-orgmode@gnu.org; Mon, 26 Dec 2016 03:49:54 -0500 Received: by mail-lf0-x242.google.com with SMTP id x140so10571027lfa.2 for ; Mon, 26 Dec 2016 00:49:54 -0800 (PST) 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: "Charles C. Berry" , joakim@verona.se Cc: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Chuck I do not blame Org at first place, but I've bisected my config and the behaviour is the same for a significant list of commits deeper in git history. And, as I've already mentioned, it started to behave as described only some time ago (about a week), after one of the package updates. Presumably the root cause can be found elsewhere... regards, Alex "Charles C. Berry" writes: > 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 =E2=80=98ob-core.e= l=E2=80=99. > 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEB3ti1VTUGbnAlLnVmGVYjLx0AQMFAlhg2a4ACgkQmGVYjLx0 AQODPwgAiKSlWYuYcdK/4ejSs4D1hMEoEmFumrDYW/08uKmZ9XmINvSZOJafQet0 zyHevKsSxKmOcRC8nifc0ItA/F1MbeAaCHaCpynWKR+bSX4tOppOmeC+v0keIKnx dCnSqj6ZaH0cwqqOyg6byyeS7koEFI81R0h6gtBS4foxleTT8yEy9jzdkoTn9rfH STMZVu6gfe0a1Id6MpyaZgGFhhMge4q57YqS9JTYOwGDCzaAGe5BD37TbsveZ8xE ilLpJh+FCXwOjM5qif0gc7TDmEXUsrjIHii2wIGOGevWmEHThzCkLuLpTrGeXrcp aPOO0zFOkm99SraC++uCte0SVYdmdA== =5osF -----END PGP SIGNATURE----- --=-=-=--