emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Charles C. Berry" <ccberry@ucsd.edu>
To: joakim@verona.se
Cc: emacs-orgmode@gnu.org
Subject: Re: Literate config and :tangle clauses
Date: Sun, 25 Dec 2016 09:52:52 -0800	[thread overview]
Message-ID: <alpine.OSX.2.20.1612250933170.1059@charles-berrys-macbook.local> (raw)
In-Reply-To: <m3tw9scmx1.fsf@chopper>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

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

  reply	other threads:[~2016-12-25 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 23:00 Literate config and :tangle clauses aaermolov
2016-12-25 10:39 ` joakim
2016-12-25 17:52   ` Charles C. Berry [this message]
2016-12-26  8:49     ` aaermolov
2016-12-26  8:33   ` aaermolov

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=alpine.OSX.2.20.1612250933170.1059@charles-berrys-macbook.local \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=joakim@verona.se \
    /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).