Tangled 0 code blocks from ahk file

Question

I am planning to (re)organize my ahk code as code blocks into an org file and tangle this file to obtain the source file.

This is my ahk-guivho.org input file, with two code blocks, empty for the sake of this post:

#+TITLE:      AHK config file
+AUTHOR:      Guido Van Hoecke
+EMAIL:       (concat "guivho" at-sign "gmail.com")

#+PROPERTY:  header-args   :tangle ahk-guivho.ahk
#+PROPERTY:  header-args+  :padline yes
#+PROPERTY:  header-args+  :eval never
#+PROPERTY:  header-args+  :eval no
#+PROPERTY:  header-args+  :exports code

* HideWindow - hides the active window
#+BEGIN_SRC ahk
  HideWindow(title="", x=0, y=0) { ;hides the active window
  }


#+END_SRC
* ActivateWindow
#+BEGIN_SRC ahk
  ActivateWindow(title="") {
  }

#+END_SRC

I expect org-babel-tangle to produce a file called ahk-guivho.ahk with two empty subs (HideWindow and ActivateWindow) but it does not.

It simply complains: Tangled 0 code blocks from ahk-guivho.org

I am pretty sure that my org and babel setup is ok: I tangle my .emacs from an org file without any problems.

I do realize that ahk is not among the officially supported languages.

But when I edit a code block from the org file, I get a buffer with ahk-mode as expected.

Do I need to initialize something somewhere to be able to tangle ahk code from an org file?

Answer 1

I'm pretty sure the problem here is that you did not refresh the buffer before tangling. You can do that by pressing C-c C-c on one of the keyword lines (a line starting with #+), because then Org mode activates changes to in-buffer settings; alternatively, you can save the file and revert the buffer from the file; or save the file, kill the buffer and reopen the file - see In buffer settings in the manual.

Here's an explanation of @gregoryg's findings in the comment: when you first add a #+PROPERTY line in the file (or you cut and paste the OP's Org mode file into a new local file), the #+PROPERTY: settings are NOT active: you need to activate them as pointed out above. So if you try to tangle before activating, you get the Tangled 0 code blocks message. If you then activate them, it all works as it should.

If OTOH you add the :tangle foo header to the code blocks instead, you don't need to activate anything: the babel code parses the code blocks in their entirety and it tangles the two code blocks successfully.

I hope that clarifies the situation.