#+include: with ``adjustable'' path (separately defined, like macro expansion)

#+include: with ``adjustable'' path (separately defined, like macro expansion)

[Martin Steffen]

Hi,

I'd like to achieve something like the following (which does not work)

#+MACRO: custompath  ~/some/place/where/the/code/resides
#+include: "{{{custompath}}}src/example.code" 


Macro-expansion generally works, but not in those circumstances. I also
seens that there's the 

#+LINK: customurl

which conceptually does such macro expansion but it seems intended for
linking in stuff, not for "embedding" pieces of code.


Is there a way to achieve what I want, which I overlooked?
Thanks, Martin

Re: #+include: with ``adjustable'' path (separately defined, like macro expansion)

[Nicolas Goaziou]

Hello,

Martin Steffen <msteffen@ifi.uio.no> writes:

> I'd like to achieve something like the following (which does not work)
>
> #+MACRO: custompath  ~/some/place/where/the/code/resides
> #+include: "{{{custompath}}}src/example.code" 
>
> Macro-expansion generally works, but not in those circumstances.

I think the manual is pretty clear about the locations where macros are
expected to work. In this case, as you noticed, they won't.

> Is there a way to achieve what I want, which I overlooked?

You can expand such INCLUDE keyword using some markup of your own and
a function within `org-export-before-processing-hook'. However, it will
not work for nested INCLUDE keywords.


Regards,

-- 
Nicolas Goaziou