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

From: Ihor Radchenko <yantar92@posteo.net>
To: reza <reza@housseini.me>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Cannot expand macros through included org file
Date: Fri, 17 Feb 2023 13:02:28 +0000	[thread overview]
Message-ID: <87bklsbg2j.fsf@localhost> (raw)
In-Reply-To: <0102018656f8a2f3-2178ae87-8ca6-4f68-9a7c-7f2676084710-000000@eu-west-1.amazonses.com>

reza <reza@housseini.me> writes:

>> It works, but Org does not include variable assignments to exported code
>> by default. See org-babel-exp-code-template. The assignment would be
>> done if you execute the blocks though.
>
> So I have to set this variable to true?

Check out the docstring.
<F1> v org-babel-exp-code-template <RET>

>> Yet another approach is including common :var year=2009 header arg.
>
> what do you mean by common? I want to have a report for the years 
> 2019-2022 for example.

report_2019.org:

#+TITLE: Report 2019
#+property: header-args :var year=2019

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

template.org:

#+TITLE: Report

* My headline

#+begin_src emacs-lisp :exports both :results value :eval yes
year
#+end_src

#+BEGIN_SRC bash
./get_log_file --start=$year-01-01 --end=$year-12-31
#+END_SRC

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


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

next prev parent reply	other threads:[~2023-02-17 13:02 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 ` Cannot expand macros through included org file reza
2023-02-15 20:44   ` 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 [this message]
     [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=87bklsbg2j.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=reza@housseini.me \
    /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).