Relative links and #+include:

Relative links and #+include:

[Pavel Panchekha]

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

I create the RSS feed for my blog with a file that #+include:'s the 
various blog posts; this way, when I export it to RSS using ox-rss.el, 
the full text of each blog post is in the feed. The feed is generated 
from a file called "/rss.org", and the blog posts themselves are 
located in "/blog/*.org".

I've noticed that when a post has a relative link to another post, 
images, or source code, that link is broken. For example, when a post 
in "/blog/zippers/huet.org" links to "kiselyov.org", which should be a 
link to the page "/blog/zippers/kiselyov.org", the link is instead 
interpreted as a link to "/kiselyov.org", since the post is being 
#+include:'d into a file in "/".

Is there any way to advise the #+include: process to resolve relative 
links correctly? Or a better way to include Org files in one another?

—Pavel Panchekha

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

Re: Relative links and #+include:

[Rasmus]

Pavel Panchekha <me@pavpanchekha.com> writes:

> Is there any way to advise the #+include: process to resolve relative
> links correctly? Or a better way to include Org files in one another?

Relative links work.  Use something like

         #+include: ./inc/o2.org

Or

        #+include: inc/o2.org

For including o2.org from the subfolder inc.

Hope it helps,
Rasmus

-- 
I hear there's rumors on the, uh, Internets. . .