emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Henney <whenney@gmail.com>
To: emacs-org <emacs-orgmode@gnu.org>
Subject: Inheritance of tangle file for org babel blocks is broken in org 9
Date: Fri, 18 Nov 2016 14:39:14 -0600	[thread overview]
Message-ID: <CAKchnZPuUjciZQ2VEOD7YSRtH_D8VfiK2LNR7Bvy43XSABeu=g@mail.gmail.com> (raw)

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

Hi,

Since upgrading to version 9.0, tangling of babel source blocks no longer
works properly for me.  Specifically, the tangle file name is not inherited
from settings in a property drawer higher up the sub-tree, so that "C-u C-u
C-c C-v C-t" no longer behaves as it should.  This worked fine in version 8
and I can't find any mention of any deliberate change in the manual or the
change log.

Here is a minimal example that explains what goes wrong.

Cheers

Will


* Test of inheritance of tangle file name
** Pieces to tangle to test-A.el
:PROPERTIES:
:header-args: :tangle test-A.el
:END:

*** Piece A1
#+BEGIN_SRC emacs-lisp
;; code-block from first sub-head of A
#+END_SRC

*** Piece A2
#+BEGIN_SRC emacs-lisp
;; code-block from second sub-head of A
#+END_SRC

** Pieces to tangle to test-B.el
:PROPERTIES:
:header-args: :tangle test-B.el
:END:

+ This does not work any more in org 9
+ The pieces are tangled to =test-A.el= instead of =test-B.el=

*** Piece B1
#+BEGIN_SRC emacs-lisp
;; code-block from first sub-head of B
#+END_SRC

*** Piece B2
#+BEGIN_SRC emacs-lisp
;; code-block from second sub-head of B
#+END_SRC

** Results of inspecting babel info in source block B1
+ =C-c C-v TAB= invokes =(org-babel-view-src-block-info)=

*** In Org 8
+ src_elisp{(org-version)} =8.2.10=
+ This looks fine

#+BEGIN_EXAMPLE
Lang: emacs-lisp
Header Arguments:
:cache no
:colnames no
:exports code
:hlines yes
:noweb no
:results replace
:session none
:tangle test-B.el
#+END_EXAMPLE

*** In Org 9
+ src_elisp{(org-version)} {{{results(=9.0.1=)}}}
+ This looks contradictory
  + The "Properties" section has ":header-args :tangle test-B.el", which is
correct
  + But the "Header Arguments" has ":tangle test-A.el", which is wrong

#+BEGIN_EXAMPLE
Lang: emacs-lisp
Properties:
:header-args :tangle test-B.el
:header-args:emacs-lisp nil
Header Arguments:
:cache no
:exports code
:hlines no
:lexical no
:noweb no
:results replace
:session none
:tangle test-A.el
#+END_EXAMPLE


-- 

  Dr William Henney, Instituto de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

[-- Attachment #2: Type: text/html, Size: 5726 bytes --]

             reply	other threads:[~2016-11-18 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 20:39 William Henney [this message]
2016-11-18 21:31 ` Inheritance of tangle file for org babel blocks is broken in org 9 Charles C. Berry
2016-11-18 23:34   ` William Henney

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='CAKchnZPuUjciZQ2VEOD7YSRtH_D8VfiK2LNR7Bvy43XSABeu=g@mail.gmail.com' \
    --to=whenney@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).