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" <ccberry@ucsd.edu> 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 ‘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