emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: reza <reza@housseini.me>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Cannot expand macros through included org file
Date: Wed, 15 Feb 2023 20:34:51 +0000	[thread overview]
Message-ID: <0102018656c98091-28c05c5e-9dbd-449a-8af2-dbe7908056c4-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: 7d032f82-9d16-edff-b548-3c01f6ea68cb@housseini.me

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

Hi List

I have the following setup:
In "template.org" is the structure of a report defined which I need to 
generate for several years, e.g:

   #+TITLE: Report

   * My headline

   #+BEGIN_SRC bash :file log_{{{year}}}.csv
     ./get_log_file --start={{{year}}}-01-01 --end={{{year}}}-12-31
   #+END_SRC

   #+BEGIN_SRC python
     log = pd.read_csv("log_{{{year}}}.csv")
   #END_SRC

Now I want to generate a report for different years, my approach was now 
to have a file "report_2019.org" like:

   #+TITLE: Report 2019
   #+MACRO: year 2019

   #+INCLUDE: "template.org" :lines "2-"


But that does not seem to work. It looks like the macro expansion does 
not happen for included content. Is this a bug or correct behavior, what 
would be the approach to not repeat the content for several reports?

Thanks for your inputs.

Cheers,
Reza

[-- Attachment #2: OpenPGP_0xC375C6AF05125C52.asc --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]

[-- Attachment #3: OpenPGP_signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

next      parent reply	other threads:[~2023-02-15 20:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7d032f82-9d16-edff-b548-3c01f6ea68cb@housseini.me>
2023-02-15 20:34 ` reza [this message]
2023-02-15 20:44   ` Cannot expand macros through included org file Ihor Radchenko
     [not found]     ` <ecd7d8ae-81de-5bb8-f66f-6bfc2152480b@housseini.me>
2023-02-15 20:53       ` reza
2023-02-15 21:10         ` Ihor Radchenko
     [not found]           ` <2b6f1944-66e1-c491-40f5-420018411312@housseini.me>
2023-02-15 21:26             ` reza
2023-02-17 13:02               ` Ihor Radchenko
     [not found]                 ` <fc618f97-e272-5773-7143-4a1381f242e6@housseini.me>
2023-02-17 13:05                   ` reza
2023-02-15 21:51         ` Nick Dokos

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=0102018656c98091-28c05c5e-9dbd-449a-8af2-dbe7908056c4-000000@eu-west-1.amazonses.com \
    --to=reza@housseini.me \
    --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

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).