From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Order of tangled blocks reversed?
Date: Sun, 7 Oct 2018 02:56:22 -0400 [thread overview]
Message-ID: <CAFyQvY1pKF3pt2Vm-L_gJgrzNQDhySmq4-j3ZXqK1WAt7bSX6Q@mail.gmail.com> (raw)
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
next reply other threads:[~2018-10-07 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 6:56 Kaushal Modi [this message]
2018-10-10 22:05 ` Order of tangled blocks reversed? Nicolas Goaziou
2018-10-10 22:15 ` Kaushal Modi
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=CAFyQvY1pKF3pt2Vm-L_gJgrzNQDhySmq4-j3ZXqK1WAt7bSX6Q@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).