From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kaushal Modi <kaushal.modi@gmail.com>
Subject: Order of tangled blocks reversed?
Date: Sun, 7 Oct 2018 02:56:22 -0400
Message-ID: <CAFyQvY1pKF3pt2Vm-L_gJgrzNQDhySmq4-j3ZXqK1WAt7bSX6Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41187)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kaushal.modi@gmail.com>) id 1g937X-0002sL-3G
	for emacs-orgmode@gnu.org; Sun, 07 Oct 2018 03:04:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kaushal.modi@gmail.com>) id 1g92zt-0000CT-HR
	for emacs-orgmode@gnu.org; Sun, 07 Oct 2018 02:57:02 -0400
Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]:38259)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <kaushal.modi@gmail.com>)
	id 1g92zt-0000Bu-9V
	for emacs-orgmode@gnu.org; Sun, 07 Oct 2018 02:57:01 -0400
Received: by mail-lj1-x22f.google.com with SMTP id v7-v6so14594259ljg.5
	for <emacs-orgmode@gnu.org>; Sat, 06 Oct 2018 23:57:01 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-org list <emacs-orgmode@gnu.org>

Hello,

I was playing with Org Tangle header-args inheritance and came up with
this example:

=====
#+property: header-args :tangle yes

At Org level 0.

* Heading 1
:PROPERTIES:
:header-args: :tangle foo.el
:END:
At Org level 1.
#+name: block1
#+begin_src emacs-lisp
(message "this will be tangled to property_drawer2.el")
#+end_src
** Heading 1.1
:PROPERTIES:
:header-args:emacs-lisp: :tangle no
:END:
At Org level 2.

Only the emacs-lisp block will *not* be tangled from this subtree.
#+name: block2
#+begin_src emacs-lisp
(message "this block will *not* be tangled")
#+end_src

But the below Nim block will tangle fine (though incorrectly to the
foo.el file!). Though, the below /block3/ appears *above* /block1/ in
the tangled file foo.el.
#+name: block3
#+begin_src nim
echo "this block will be tangled to property_drawer2.nim"
#+end_src
=====

Tangling this (C-c C-v t) gives this foo.el file:

=====
echo "this block will be tangled to property_drawer2.nim"

(message "this will be tangled to property_drawer2.el")
=====

Ignoring that Nim code gets inserted into the Emacs-Lisp file because
of incorrect :tangle header-args under Heading 1, why is the block3
code appearing above block1?

Is this a bug?

Org mode version 9.1.14 (release_9.1.14-933-gfe72a0 @
/home/kmodi/usr_local/apps/6/emacs/master/share/emacs/site-lisp/org/)


--
Kaushal Modi